[ODK Community] ODK Collect File Save Name

David,

This feature was originally requested a few years ago (see
https://code.google.com/p/opendatakit/issues/detail?id=433), but the
work has yet to be started by the core team because it's not high
priority. Star that issue to get updates, or if you need this feature
soon, hire a developer at http://opendatakit.org/help/help-for-hire/
to build it.

Yaw

··· -- Need ODK help? Go to http://nafundi.com for custom development, form design, implementation support, and user training for ODK.

On Thu, Feb 28, 2013 at 11:10 AM, davidperrin.nc@gmail.com wrote:

In Collect, once a orm is completed, they are saved as the original form name plus a date stamp.

I see the prompt to 'rename' the file just before saving a completed form.

Question:
Can the file name itself be created from an extracted field in the just completed form?

I'm performing a household survey, and instead of manually renaming the file just before saving, to differentiate all the saved filled out forms, would it be possible to extract a field (example: household_ID), and save the form with that auto-generated name?

I'm guessing this isn't possible, or would require custom modification of the Collect programming code?

Thanks for any insights in advance!

David

--

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/groups/opt_out.

Actually, it will be out with the next ODK Collect release (no ETA on
that)...

I have code checked into the ODK Collect main branch that will use the
value of the meta/instanceName, if present and not an empty string, as the
name of the instance.
The expectation is you would define this as a calculated expression
(analogous to the meta/instanceID field) based upon the fields you want to
use.

If this field is defined and non-null, the user will be unable to edit or
alter the name of the instance. If it is absent or an empty string, then
the user would be able to specify a name.

The next ODK Collect release will also support itext tags for constraint
messages and required messages (so you can say "item foo is required" not
just have "this field is required" show on a field-list, and have to guess
what field caused that error).

Other than various updates to languages, the remaining item for the next
ODK Collect roll-out (1.3) is device printing. We have prototype code of
this, based upon an early ODK Sensors implementation, but it needs some
further clean-up and some thought on how you'd define such a widget in
XForms. Device printing would allow ODK Collect to, potentially, generate
barcode labels on-the-fly. Time is not in my favor.

Mitch

··· On Thu, Feb 28, 2013 at 11:19 AM, Yaw Anokwa wrote:

David,

This feature was originally requested a few years ago (see
https://code.google.com/p/opendatakit/issues/detail?id=433), but the
work has yet to be started by the core team because it's not high
priority. Star that issue to get updates, or if you need this feature
soon, hire a developer at http://opendatakit.org/help/help-for-hire/
to build it.

Yaw

Need ODK help? Go to http://nafundi.com for custom development, form
design, implementation support, and user training for ODK.

On Thu, Feb 28, 2013 at 11:10 AM, davidperrin.nc@gmail.com wrote:

In Collect, once a orm is completed, they are saved as the original form
name plus a date stamp.

I see the prompt to 'rename' the file just before saving a completed
form.

Question:
Can the file name itself be created from an extracted field in the just
completed form?

I'm performing a household survey, and instead of manually renaming the
file just before saving, to differentiate all the saved filled out forms,
would it be possible to extract a field (example: household_ID), and save
the form with that auto-generated name?

I'm guessing this isn't possible, or would require custom modification
of the Collect programming code?

Thanks for any insights in advance!

David

--

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/groups/opt_out.

--

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/groups/opt_out.

--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com

Mitch,

Many thanks!! That's exactly what I'm looking for. I'll be waiting for
that next release :slight_smile:

Best,
David

··· On Thursday, February 28, 2013 2:27:21 PM UTC-5, Mitch wrote: > > Actually, it will be out with the next ODK Collect release (no ETA on > that)... > > I have code checked into the ODK Collect main branch that will use the > value of the meta/instanceName, if present and not an empty string, as the > name of the instance. > The expectation is you would define this as a calculated expression > (analogous to the meta/instanceID field) based upon the fields you want to > use. > > If this field is defined and non-null, the user will be unable to edit or > alter the name of the instance. If it is absent or an empty string, then > the user would be able to specify a name. > > The next ODK Collect release will also support itext tags for constraint > messages and required messages (so you can say "item foo is required" not > just have "this field is required" show on a field-list, and have to guess > what field caused that error). > > Other than various updates to languages, the remaining item for the next > ODK Collect roll-out (1.3) is device printing. We have prototype code of > this, based upon an early ODK Sensors implementation, but it needs some > further clean-up and some thought on how you'd define such a widget in > XForms. Device printing would allow ODK Collect to, potentially, generate > barcode labels on-the-fly. Time is not in my favor. > > Mitch > > On Thu, Feb 28, 2013 at 11:19 AM, Yaw Anokwa <yan...@nafundi.com wrote: > >> David, >> >> This feature was originally requested a few years ago (see >> https://code.google.com/p/opendatakit/issues/detail?id=433), but the >> work has yet to be started by the core team because it's not high >> priority. Star that issue to get updates, or if you need this feature >> soon, hire a developer at http://opendatakit.org/help/help-for-hire/ >> to build it. >> >> Yaw >> -- >> Need ODK help? Go to http://nafundi.com for custom development, form >> design, implementation support, and user training for ODK. >> >> On Thu, Feb 28, 2013 at 11:10 AM, <davidpe...@gmail.com > wrote: >> > In Collect, once a orm is completed, they are saved as the original >> form name plus a date stamp. >> > >> > I see the prompt to 'rename' the file just before saving a completed >> form. >> > >> > Question: >> > Can the file name itself be created from an extracted field in the just >> completed form? >> > >> > I'm performing a household survey, and instead of manually renaming the >> file just before saving, to differentiate all the saved filled out forms, >> would it be possible to extract a field (example: household_ID), and save >> the form with that auto-generated name? >> > >> > I'm guessing this isn't possible, or would require custom modification >> of the Collect programming code? >> > >> > Thanks for any insights in advance! >> > >> > David >> > >> > -- >> > -- >> > Post: opend...@googlegroups.com >> > Unsubscribe: opendatakit...@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...@googlegroups.com . >> > For more options, visit https://groups.google.com/groups/opt_out. >> > >> > >> >> -- >> -- >> Post: opend...@googlegroups.com >> Unsubscribe: opendatakit...@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...@googlegroups.com . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > -- > Mitch Sundt > Software Engineer > University of Washington > mitche...@gmail.com

Hi David,

Have you tried this feature? does it work with ODK Collect 1.4?

Regards,
Ayub

Ayub,

It does work.

Yaw

··· -- Need ODK services? http://nafundi.com provides form design, server setup, professional support, and software development for ODK.

On Fri, Dec 13, 2013 at 8:32 AM, Ayub nrspaggregate@gmail.com wrote:

Hi David,

Have you tried this feature? does it work with ODK Collect 1.4?

Regards,
Ayub

--

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/groups/opt_out.