dhis2-devs team mailing list archive

[Knut Staring <knutst@xxxxxxxxx>]

On Sat, May 2, 2009 at 1:03 PM, ola testuser <olati@xxxxxxxxxx> wrote:

> Hi,
>
> I don't agree with this. A solution to this is to use a prefix of the
> parent's name in the name of the children.


I have seen this practice, e.g. in the sample database. In my opinion, it's
a horrible pollution of the perfectly good data.


> Orgunit names should be unique to avoid having a chaotic/messy database.


It is rather the current pollution kludge of names that is causing a mess.


> Data values in the database are described by the data element + the period
> +
> the orgunit.
>

Yes, but you will still have three options for uniqueness:
1) UUID  2) organisationunitid 3) parentid +name

Knut


> Orgunit hierarchy is not referenced from the data values so the
> proposed change would easily cause problems when dealing with the data.
>
> best regards,
> Ola Hodne Titlestad
> HISP
> University of Oslo
>
>
> On Sat, May 2, 2009 at 1:46 PM, Knut Staring <knutst@xxxxxxxxx> wrote:
>
> > Public bug reported:
> >
> > Currently, the name field in organisationunit have been set to be
> > unique. This uniqueness constraint should only apply within the scope of
> > the parent, i.e. it is the *combination* of the "name" and the
> > "parentid" fields that should be unique.
> >
> > ** Affects: dhis2
> >     Importance: Undecided
> >         Status: New
> >
> > --
> > orgunitname uniqueness should only be among siblings
> > https://bugs.launchpad.net/bugs/370791
> > You received this bug notification because you are a member of DHIS 2
> > coordinators, which is the registrant for DHIS.
> >
> > Status in District Health Information Software 2: New
> >
> > Bug description:
> > Currently, the name field in organisationunit have been set to be unique.
> > This uniqueness constraint should only apply within the scope of the
> parent,
> > i.e. it is the *combination* of the "name" and the "parentid" fields that
> > should be unique.
> >
>
> --
> orgunitname uniqueness should only be among siblings
> https://bugs.launchpad.net/bugs/370791
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in District Health Information Software 2: New
>
> Bug description:
> Currently, the name field in organisationunit have been set to be unique.
> This uniqueness constraint should only apply within the scope of the parent,
> i.e. it is the *combination* of the "name" and the "parentid" fields that
> should be unique.
>


-- 
Cheers,
Knut Staring

-- 
orgunitname uniqueness should only be among siblings
https://bugs.launchpad.net/bugs/370791
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.

Status in District Health Information Software 2: New

Bug description:
Currently, the name field in organisationunit have been set to be unique. This uniqueness constraint should only apply within the scope of the parent, i.e. it is the *combination* of the "name" and the "parentid" fields that should be unique.