Hi 2009/3/18 Lars Helge Øverland <larshe...@gmail.com>: > >> >> OK, after much poking around the schema, I realize that I have >> misinterpreted something. You have to impose one of two constraints. >> Either: >> 1. A DataElement can only (must) be a member of one DataSet; or >> 2. A DataElement can only (must) have one PeriodType. > > > True. > >> >> If we cannot impose (1), or we shouldn't or we don't want to, then is >> it instead possible to think of a "fully qualified" DataElement as >> DataSet::DataElement? Practically this means having DataSet, >> DataElement and Period association with the DataValue. The advantage >> would be that we still only need to associate the PeriodType with the >> DataSet. > > > > Enforcing 1) cannot be done, as data elements frequently appear in multiple > datasets, which is a part of the HISP "appproach".
Then we must indeed do as you suggest. Regards Bob > >> >> PS. I am still looking for sample datasets. I tried the link at >> http://208.76.222.114/confluence/display/DHIS2/Downloads but it is >> broken. Can anyone please point me to some. > > You can find a postgres backup of the sample database here: > http://folk.uio.no/larshelg/files/dhis2sample.backup. > > I will create a mysql dump later today and let you know:) > > > Lars > > _______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : dhis2-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp