dhis2-devs team mailing list archive

[Kim-Anh Vo <catakim@xxxxxxxxx>]

Hi all,

The subject I have given out: "Dataset vs. import/export vs. dael-dataset
integrity checking" appears when I am working on building an
integrated-health database.

The points for the above objects:
1. Dataset (or discussed as dataelementSet): is a list of dataelements for
entry, import/export, etc.
2. Import/Export datavalue (or maybe called dataelementValue) is based on
dataset, it means that dataelement value is only exported/imported by being
included in at least one dataset.
3. Dataset-integrity checking to find the violate: *Data elements assigned
to data sets with different period types*

See the above under a data warehouse (or just a central data repository)
situation: all daels, datavalues, etc. from local databases would be
imported into that sys.

Back to the objects vs. DHIS2, there are some issues:

*iss1)* Data (dataelementvalue) imported from many sources from diff local
places (nations, provinces, dis., etc.) SO a unified dataset with a unified
period for all is unlikely possible. As a result of this," dael-dataset
integrity checking" criterion is hard to be fulfilled

*iss2)* Data import/export all the time goes with datasets so everytime
importing/exporting datavalues, dataset is an attached element for the tasks
with the additionally important info: period, ou, etc. of the dataelements.
So, whether the repository (data warehouse) needs that local dataset or not
they (reluctantly-imported-dataset) do exist!
And of course, as a central data house/repository: import/export is a basic
function, so will we find another criterion for checking-out the
dael-dataset-integrity for a data warehouse/repository?

Any ideas?

-- 
-- 
Best regards,
Kim-Anh Vo

+84.906612246
kavo@xxxxxxxxxx
Coordinator of HISP(hisp.info) in Vietnam
Master of Information Systems
at the University of Oslo
------------------------------------
join facebook at www.facebook.com join LinkedIn at www.linkedin.com