dhis2-users team mailing list archive

[Bob Jolliffe <bobjolliffe@xxxxxxxxx>]

I think of the numbers are small you are best just to maintain two
different dataelementgroups of datalements with names/codes which are
related.

I don't think this is really a versioning problem as you describe it.
Unless you are planning to go on and make more versions.  It is
similar to the problem of comparing aggregate reported data with data
which has been aggregated from an EMR.

Failing which, the attributeoptioncombo or categoryoptioncombo is the
only other dimension you do have to play with if you want to tag the
same dataelements differently.

On 14 November 2017 at 21:27, Adam Preston <adam704a@xxxxxxxxxxx> wrote:
> Greetings from Colorado, USA.
>
> I have a project that would like to maintain different versions of the data
> in DHIS2. For example, they have a bunch of data elements they are getting
> externally and these would be considered as one version, they do a bunch of
> cleaning and this would be another version. So when running the reports they
> would select the version of the data. How can I do this?
>
>
> Sent from Outlook
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-users
> Post to     : dhis2-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-users
> More help   : https://help.launchpad.net/ListHelp
>