Hi Tran, Archiving is good idea. And I would suggest archiving based on the status of the programInstance not programStageInstance. For example, to generate visit plans we will rely on previously completed programStageInstances, therefore better if we could keep completed programStageInstances as long as their parent programInstance is active. If we want to play around with history (within the current programInstance at least), then we will definately need completed programStageInstances of the current programInstance.
If a programInstance is successfully completeed (or terminated for some reason), we will always start a new cycle of programInstance by keepin aside the previous programInstance. Abyot. On Fri, Oct 22, 2010 at 9:29 AM, Chau Thu Tran <[email protected]>wrote: > Hi all, > > How do you think if we archive data values according to DueDate and > Completed property of ProgramStageInstance ? > > Use choose interval, the system will check DueDate and the status of > ProgramStageInstance, if DueDate is ok and status is completed, then archive > all of data values of the instance. > > Best regards, > ------------------------------------------------ > Châu Thu Trân > HISP Viet Nam > Email: [email protected] > Cell phone: +84 97 324 1542 > > > 2010/10/21 Lars Helge Øverland <[email protected]> > >> Blueprint changed by Lars Helge Øverland: >> >> Assignee: (none) => Thu Tran >> >> -- >> Patient datavalue archive >> https://blueprints.launchpad.net/dhis2/+spec/patient-datavalue-archive >> > >
_______________________________________________ Mailing list: https://launchpad.net/~dhis2-devs Post to : [email protected] Unsubscribe : https://launchpad.net/~dhis2-devs More help : https://help.launchpad.net/ListHelp
