With reference to my earlier post I have a follow up question.
From what I can see the naming convention for saved instances in the
/odk//instances/ directory is as follows:
[form name]-[date and time it was finalised].xml
There is nothing in the name which makes it unique. I have a feeling
this naming convention is used because it is the only piece of
metatada that shows when the form was finalised.
I have a number of devices that wil be running one of our custom
applications generating instance files containing environment
sensor readings. Using the naming convention above, it is likely that
two devices will generate an instance with the same name.
To make it easier to collect all of the responses, and to implement
distributed storage of instance files, I'm storing copies of all of
the instance files from all of the devices in my mesh network into the
/odk/instances/ directory on each device.
I have a feeling the naming convention is significant because it is
the only piece of metatada that shows when the form was finalised.
However, the lack of guaranteed unique names is a concern.
With this in mind, I was wondering if I can add a third field which
would be the device id of the collecting device. The naming convention
for these instance files would become:
[form name]-[date and time it was finalised]-[device id].xml
Is this going to break anything? Especially the collection of
instances using ODK Collect and then the subsequent upload into ODK
Alternate strategies for unique names are very welcome.