I have a question regarding data-entry module and its roadmap. Currently, we have a webapp that uses a resource included in this module to provide the users with a dataset form template. It is “/dhis-web-dataentry/loadForm.action?dataSetId=<data_set_id>”.
Our app relies completely on this resource, and we would like to know the time frame for data-entry module (and everything in it) to be transformed in a WebApp. Also if a new mechanism to obtain the dataset form template will be implemented, I mean, an new API endpoint or a javascript function that returns the dataset form template properly formatted (sections, category combos, etc) in the same way that “loadForm.action” does now.
Does someone have any insight on this issue? At least if data-entry module is going to be deprecated in the short-term, or if a built-in mechanism to obtain the dataset form template will be implemented.
I have a question regarding data-entry module and its roadmap. Currently, we have a webapp that uses a resource included in this module to provide the users with a dataset form template. It is “/dhis-web-dataentry/loadForm.action?dataSetId=<data_set_id>”.
Our app relies completely on this resource, and we would like to know the time frame for data-entry module (and everything in it) to be transformed in a WebApp. Also if a new mechanism to obtain the dataset form template will be implemented, I mean, an new API endpoint or a javascript function that returns the dataset form template properly formatted (sections, category combos, etc) in the same way that “loadForm.action” does now.
Does someone have any insight on this issue? At least if data-entry module is going to be deprecated in the short-term, or if a built-in mechanism to obtain the dataset form template will be implemented.
I have a question regarding data-entry module and its roadmap. Currently, we have a webapp that uses a resource included in this module to provide the users with a dataset form template. It is “/dhis-web-dataentry/loadForm.action?dataSetId=<data_set_id>”.
Our app relies completely on this resource, and we would like to know the time frame for data-entry module (and everything in it) to be transformed in a WebApp. Also if a new mechanism to obtain the dataset form template will be implemented, I mean, an new API endpoint or a javascript function that returns the dataset form template properly formatted (sections, category combos, etc) in the same way that “loadForm.action” does now.
I don’t think we have any immediate plans of removing the data entry module, at some point I’m sure we want to replace it (using the same frameworks as the maintenance app etc), but I’m not sure when that will happen (and we will provide a similar API when that happens)
That said, have you had a look at how our field API works? it should be possible to get more or less exactly what you need by doing /api/dataSets/ID?fields=id,displayName,section[:owner] etc
Does someone have any insight on this issue? At least if data-entry module is going to be deprecated in the short-term, or if a built-in mechanism to obtain the dataset form template will be implemented.
I have a question regarding data-entry module and its roadmap. Currently, we have a webapp that uses a resource included in this module to provide the users with a dataset form template. It is “/dhis-web-dataentry/loadForm.action?dataSetId=<data_set_id>”.
Our app relies completely on this resource, and we would like to know the time frame for data-entry module (and everything in it) to be transformed in a WebApp. Also if a new mechanism to obtain the dataset form template will be implemented, I mean, an new API endpoint or a javascript function that returns the dataset form template properly formatted (sections, category combos, etc) in the same way that “loadForm.action” does now.
With the API it is possible to obtain all the information about a dataset (section, dataelements, categories, etc), but I am looking for the dataset form with a similar appearance as in the dataentry. I mean, a form with a table with cells properly merged when two or more categories are present, and with greyed cells when necessary.
But at the moment it is enough to know that there is not immediate plan of removing it.
Thanks!
···
On 30 July 2016 at 11:06, Morten Olav Hansen morten@dhis2.org wrote:
Hi Victor
I don’t think we have any immediate plans of removing the data entry module, at some point I’m sure we want to replace it (using the same frameworks as the maintenance app etc), but I’m not sure when that will happen (and we will provide a similar API when that happens)
That said, have you had a look at how our field API works? it should be possible to get more or less exactly what you need by doing /api/dataSets/ID?fields=id,displayName,section[:owner] etc
Does someone have any insight on this issue? At least if data-entry module is going to be deprecated in the short-term, or if a built-in mechanism to obtain the dataset form template will be implemented.
I have a question regarding data-entry module and its roadmap. Currently, we have a webapp that uses a resource included in this module to provide the users with a dataset form template. It is “/dhis-web-dataentry/loadForm.action?dataSetId=<data_set_id>”.
Our app relies completely on this resource, and we would like to know the time frame for data-entry module (and everything in it) to be transformed in a WebApp. Also if a new mechanism to obtain the dataset form template will be implemented, I mean, an new API endpoint or a javascript function that returns the dataset form template properly formatted (sections, category combos, etc) in the same way that “loadForm.action” does now.