Hi All,
I'm just moving my first steps into ODK and facing the following problem:
assume that I fill a form and mark it as finalized, is there a way to prevent accidental editing of it?
I can edit both saved and finalized forms in ODK Collect using 'Edit saved forms' but there is no 'View finalized forms' where I can safely browse through finalized forms in read-only mode.
Any direction about customizing FormEntryActivity somehow to get a viewer out of it?
Regards.
Antonio.
Hi Antonio,
One thing you could do is turn on finalized by default and auto-send.
If you have connectivity, it tends to send forms as soon as they are
finalized.
If you want to get a true read-only view of forms, easiest thing to do
is copy the Edit Saved Forms vertical view and remove the launching of
the form that happens there. You could also remove saving from
FormEntryActivity and make all widgets readonly.
If you have other code questions, send them to
opendatakit-developers@googlegroups.com.
Yaw
On Mon, May 19, 2014 at 8:26 AM, antonio.toma@gmail.com wrote:
Hi All,
I'm just moving my first steps into ODK and facing the following problem:
assume that I fill a form and mark it as finalized, is there a way to prevent accidental editing of it?
I can edit both saved and finalized forms in ODK Collect using 'Edit saved forms' but there is no 'View finalized forms' where I can safely browse through finalized forms in read-only mode.
Any direction about customizing FormEntryActivity somehow to get a viewer out of it?
Regards.
Antonio.--
Post: opendatakit@googlegroups.com
Unsubscribe: opendatakit+unsubscribe@googlegroups.com
Options: http://groups.google.com/group/opendatakit?hl=en
You received this message because you are subscribed to the Google Groups "ODK Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to opendatakit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Yaw,
I'm following the 'make everything readonly' path and it looks good so far.
I'll move to the opendatakit-developers mailing list for further discussion.
Thanks for your answer.
Regards.
Antonio.
Hi Antonio, Iwa wondering if you had followed through with this implementation.
I was looking into a way for my users to review sent forms (read-only), a function not available in Collect at the time, which seams very close from what you were intending to do.
Thanks for any info that might help.
Hi Antonio, I wondered if you followed throuh on your idea of implementing a "View readonly finalized forms" function.
This would be helpful for my project. Thanks
Hi Gwenael,
sorry for the late reply.
A long time has passed since I investigated ODK and, in the end, we
implemented the functionality on our own.
We had simple requirements and integrating ODK looked like a bit of
overkill in our case.
We developed a simple JSON representation of the form structure, and
payload.
The form structure can be configured on the server and then retrieved
and rendered by custom code on the client on both Android and iOS.
Then the client collects form data, builds a JSON payload and sends it
back to the server were it is stored and can be reviewed.
Making the payload read only for review, after uploading it to the
server was part of the client application.
You can have a look at the resulting application Open Tenure (e.g. on
Google Play).
You can also get the source code related to this 'dynamic form' feature
at:
Please, let me know if you need more information.
Regards.
Antonio
Hi Gwenael,
sorry for the late reply.
A long time has passed since I investigated ODK and, in the end, we
implemented the functionality on our own.
We had simple requirements and integrating ODK looked like a bit of
overkill in our case.
We developed a simple JSON representation of the form structure, and
payload.
The form structure can be configured on the server and then retrieved
and rendered by custom code on the client on both Android and iOS.
Then the client collects form data, builds a JSON payload and sends it
back to the server were it is stored and can be reviewed.
Making the payload read only for review, after uploading it to the
server was part of the client application.
You can have a look at the resulting application Open Tenure (e.g. on
Google Play).
You can also get the source code related to this 'dynamic form' feature
at:
Please, let me know if you need more information.
Regards.
Antonio
Hi Antonio, thanks for the reply and the detailed description of the
implementation you put in place.
It's a bit complicated for us to change tools, so we'll find a way around
and hope for a quick implemenation of the "review sent form" function in
Collect.
Have a great week-end.
Hi Gwenael,
sorry for the late reply.
A long time has passed since I investigated ODK and, in the end, we
implemented the functionality on our own.
We had simple requirements and integrating ODK looked like a bit of
overkill in our case.
We developed a simple JSON representation of the form structure, and
payload.
The form structure can be configured on the server and then retrieved and
rendered by custom code on the client on both Android and iOS.
Then the client collects form data, builds a JSON payload and sends it
back to the server were it is stored and can be reviewed.
Making the payload read only for review, after uploading it to the server
was part of the client application.
You can have a look at the resulting application Open Tenure (e.g. on
Google Play).You can also get the source code related to this 'dynamic form' feature
at:
https://github.com/OpenTenure/ot-android/tree/master/src/org/fao/sola/clients/android/opentenure/formPlease, let me know if you need more information.
Regards.
AntonioIl 02/07/2015 18:44, gwenael.prie@gmail.com ha scritto:
Hi Antonio, I wondered if you followed throuh on your idea of
implementing a "View readonly finalized forms" function.
This would be helpful for my project. Thanks
--
Gwenael Prié
ICT4D and WASH consulting+33 6 28 23 77 52 - skype:
gwen-parishttp://www.linkedin.com/in/gwenaelprie
http://www.linkedin.com/in/gwenaelprie