Oh wow, that simple? Sourceid = organisationunitid?
Thanks for the quick response David. For some reason I was expecting organisationunitid to be present in the datavalue table. Do you know the reason it’s called sourceid?
sourceid is available for distinguishing different types of organizationunit. It is one of id available since DHIS 1. In some of the DHIS2 releases, it was removed and later on it was found very useful, so it was included. It’s like parent to organisationunit.
Oh wow, that simple? Sourceid = organisationunitid?
Thanks for the quick response David. For some reason I was expecting organisationunitid to be present in the datavalue table. Do you know the reason it’s called sourceid?
sourceid is available for distinguishing different types of organizationunit. It is one of id available since DHIS 1. In some of the DHIS2 releases, it was removed and later on it was found very useful, so it was included. It’s like parent to organisationunit.
Oh wow, that simple? Sourceid = organisationunitid?
Thanks for the quick response David. For some reason I was expecting organisationunitid to be present in the datavalue table. Do you know the reason it’s called sourceid?
Subject: Re: [Dhis2-devs] Getting the OU for items recorded in datavalues table
sourceid is available for distinguishing different types of organizationunit. It is one of id available since DHIS 1. In some of the DHIS2 releases, it was removed and later on it was found very useful, so it was included. It’s like parent to organisationunit.
Oh wow, that simple? Sourceid = organisationunitid?
Thanks for the quick response David. For some reason I was expecting organisationunitid to be present in the datavalue table. Do you know the reason it’s called sourceid?
Oh wow, that simple? Sourceid = organisationunitid?
Thanks for the quick response David. For some reason I was expecting organisationunitid to be present in the datavalue table. Do you know the reason it’s called sourceid?
Incorrect - the term “sourceid” has never been used in DHIS v1. DHIS1 introduced and maintained the principle that the id reference field for any table would be called id.
I’m not sure WHY it was decided at the time to change this principle for some of the organisationunitid foreign key fields, but the idea was dropped quickly. Ola or Lars might recall…
sourceid is available for distinguishing different types of organizationunit. It is one of id available since DHIS 1. In some of the DHIS2 releases, it was removed and later on it was found very useful, so it was included. It’s like parent to organisationunit.
Oh wow, that simple? Sourceid = organisationunitid?
Thanks for the quick response David. For some reason I was expecting organisationunitid to be present in the datavalue table. Do you know the reason it’s called sourceid?
Incorrect - the term “sourceid” has never been used in DHIS v1. DHIS1 introduced and maintained the principle that the id reference field for any table would be called id.
I’m not sure WHY it was decided at the time to change this principle for some of the organisationunitid foreign key fields, but the idea was dropped quickly. Ola or Lars might recall…
sourceid is available for distinguishing different types of organizationunit. It is one of id available since DHIS 1. In some of the DHIS2 releases, it was removed and later on it was found very useful, so it was included. It’s like parent to organisationunit.
Oh wow, that simple? Sourceid = organisationunitid?
Thanks for the quick response David. For some reason I was expecting organisationunitid to be present in the datavalue table. Do you know the reason it’s called sourceid?
Oh wow, that simple? Sourceid = organisationunitid?
Thanks for the quick response David. For some reason I was expecting organisationunitid to be present in the datavalue table. Do you know the reason it’s called sourceid?
source is the main inception point of DHIS development then period means time frame then elements means cell then datasets which combines source, time, elements in unified form. most of the time we are working on data collection in health domain perhaps this combination has capacity to solve Nth dimension theorem of Mathematica. The probable reason behind unification of three independent frames is to understand nature of medium or you can say like in the form of organizationunit.
Oh wow, that simple? Sourceid = organisationunitid?
Thanks for the quick response David. For some reason I was expecting organisationunitid to be present in the datavalue table. Do you know the reason it’s called sourceid?