I have been evaluating the current features and found two candidates that don’t seem much used and could potentially be removed.
In data administration module we have “data archive” and “person data archive” functions. These will move data from the datavalue table to another datavalue archive table. These functions are not really feasible anymore now that no aggregation happens directly against the datavalue table - we recommend just keeping all data in the datavalue table as performance won’t be affected much.
Are anyone using these? Can they be removed for version 2.12?
Is there any other way to pack up all of the information about a single person and move it to another system (DHIS or other)?
Ideally, everything will be in the same database but some people may have separate instances of DHIS and need to move patients from one system to another. For instance, immunization records.
.mark
···
On Thu, Apr 25, 2013 at 6:45 AM, Lars Helge Øverland larshelge@gmail.com wrote:
Hi all,
I have been evaluating the current features and found two candidates that don’t seem much used and could potentially be removed.
In data administration module we have “data archive” and “person data archive” functions. These will move data from the datavalue table to another datavalue archive table. These functions are not really feasible anymore now that no aggregation happens directly against the datavalue table - we recommend just keeping all data in the datavalue table as performance won’t be affected much.
Are anyone using these? Can they be removed for version 2.12?
yes we are working on import-export of tracker data. Its not there at the moment but will be gradually introduced in 2.12 and 2.13.
The archiving is not much help in this regard so not exactly related.
cheers
Lars
···
On Thu, Apr 25, 2013 at 5:58 PM, Mark Spohr mhspohr@gmail.com wrote:
Hi Lars,
Just a thought.
Is there any other way to pack up all of the information about a single person and move it to another system (DHIS or other)?
Ideally, everything will be in the same database but some people may have separate instances of DHIS and need to move patients from one system to another. For instance, immunization records.
.mark
On Thu, Apr 25, 2013 at 6:45 AM, Lars Helge Øverland larshelge@gmail.com wrote:
Hi all,
I have been evaluating the current features and found two candidates that don’t seem much used and could potentially be removed.
In data administration module we have “data archive” and “person data archive” functions. These will move data from the datavalue table to another datavalue archive table. These functions are not really feasible anymore now that no aggregation happens directly against the datavalue table - we recommend just keeping all data in the datavalue table as performance won’t be affected much.
Are anyone using these? Can they be removed for version 2.12?
On Thu, Apr 25, 2013 at 5:58 PM, Mark Spohr mhspohr@gmail.com wrote:
Hi Lars,
Just a thought.
Is there any other way to pack up all of the information about a single person and move it to another system (DHIS or other)?
Ideally, everything will be in the same database but some people may have separate instances of DHIS and need to move patients from one system to another. For instance, immunization records.
.mark
On Thu, Apr 25, 2013 at 6:45 AM, Lars Helge Øverland larshelge@gmail.com wrote:
Hi all,
I have been evaluating the current features and found two candidates that don’t seem much used and could potentially be removed.
In data administration module we have “data archive” and “person data archive” functions. These will move data from the datavalue table to another datavalue archive table. These functions are not really feasible anymore now that no aggregation happens directly against the datavalue table - we recommend just keeping all data in the datavalue table as performance won’t be affected much.
Are anyone using these? Can they be removed for version 2.12?
