dhis2-devs-core team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

On Dec 4, 2013 9:52 PM, "Jim Grace" <jimgrace@xxxxxxxxx> wrote:
>
> On Wed, Dec 4, 2013 at 2:13 PM, Lars Helge Øverland <larshelge@xxxxxxxxx>
wrote:
>
>> Yes definitely, we need a "label" setting letting people choose what to
display in the UI.
>>
>>>
>>> I hope we we can allow the user to configure named relationships
between tracker entities of the same and/or different type, like optional
family relationships between Persons, or a mandatory relationship between
Sample and Person.
>>
>>
>> I think we actually have that already, look under Relationship Type in
Persons and Programs module.
>
>
> Excellent. Then we might want to extend this to include relationships
between different types of entities, and whether or not they are required,
many-to-many, etc. (e.g. a person can have zero or more siblings but a
sample must relate to exactly one patient.)
>
>>
>> Can anyone think of a good name for the Java class representing this
thing? We cannot call it Patient anymore for sure.
>
>
> Here are my top 3, each with pros and cons (not ranked):
>
> Entity - Very generic, somewhat descriptive, rather vague.

> TrackerEntity - Nice and specific, although 5 syllables is a lot.
> Tracked - A thing that is tracked. 1 syllable! perhaps too cryptic?

I like this. What about a new mix:

TrackedEntity

?

>
> Are we thinking of making "Program" into a user-configurable object as
well? (either the same type of object that a "Person" could be, or a
different type of object.) Then we can allow the user to define sensible
relationships between Person and Program and/or between lab Sample and
SampleFlow, or whatever else they need.
>
>  On Wed, Dec 4, 2013 at 3:01 PM, Ola Hodne Titlestad <olati@xxxxxxxxxx
> wrote:
>
>> Yes. There is actually a big CDC Global Health Security project that
uses Tracker exactly for this purpose. It is being piloted in Uganda.
>
>
> Very cool!
>
> Cheers,
> Jim
>