dhis2-devs-core team mailing list archive

[Morten Olav Hansen <mortenoh@xxxxxxxxx>]

We already have a blueprint on this [1], I can take on the job of changing
the web-api (require orgUnit in enrollment, and remove orgUnit from
trackedEntityInstance), if someone else can take care of SQL upgrade.. that
would be good, since its not really what I'm good at..

I guess we should default all old enrollments to be tei.orgUnit, and then
also remove tei.orgUnit from the table

Abyot also need to update his apps, so that he is sending this new orgUnit
ptr.. what about others? thoughtworks? Maybe we should send out a message
on the dev list also

--
Morten

On Tue, Mar 3, 2015 at 7:59 PM, Lars Helge Øverland <larshelge@xxxxxxxxx>
wrote:

> Hi devs,
>
> on the last meeting we discussed removing the org unit association on
> tracked entity instance, and rather have it on program instance
> (enrollment).
>
> This means we can capture where enrollments for multiple programs took
> place for a person, and sounds like a sensible thing to do.
>
> Should we go ahead?
>
> Who is most suited to take this on, Abyot, Morten?
>
> Lars
>
> --
> 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
>
>