dhis2-devs-core team mailing list archive

[Bob Jolliffe <bobjolliffe@xxxxxxxxx>]

I don't like this name at all :-(

I am not sure there is anything about this new entity object which
logically ties it to tracking. So for example such an object could serve
equally well as a base class for an orgunit or other dhis2 metadata objects
in any future refactoring.  Isn't the key innovation that it is an object
with minimal fixed properties?

So I would be in favour of a more generic name which reflects more what
this class will actually do rather than which area you see it its current
specific use (things to be tracked).

Something along the lines of DynamicEntity (or DynamicObject) or the like
makes sense.   Of course you can layer tracked things on top of that.

A passing thought (which also relates to other "complex" objects whose
attributes are spread across multiple tables) is that this might also be an
opportunity to also address the problem of how to determine "lastUpdated"
on such objects.  Recall that this is an outstanding concern currently with
orgunits making correct facility registry implementation impossiible.

So perhaps again this is an opportunity to address the concerns in the
current discussion in as general a way as possible so that we can try and
reap benefits across the system.

Bob


On 6 December 2013 17:45, Morten Olav Hansen <mortenoh@xxxxxxxxx> wrote:

>
> On Fri, Dec 6, 2013 at 1:56 PM, Jim Grace <jimgrace@xxxxxxxxx> wrote:
>
>>  TrackedEntity
>>>
>> +1
>
> --
> Morten
>
> --
> Mailing list: https://launchpad.net/~dhis2-devs-core
> Post to     : dhis2-devs-core@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs-core
> More help   : https://help.launchpad.net/ListHelp
>
>