@LN ,
I just read the Spec Proposal and this is a lot more complicated than I initially thought. Was this ever resolved or implemented?
I appreciate all of the work that has been done on this. It actually expresses much of the frustration that I've had using forms with an enumorator that is not fully literate. My project is not a large scale implementation, but I'm working with trees and doing surveys over a period of time following hundreds (and hopefully in the future thousands) of trees. Every tree we're working with has a unique ID#, but I've had to add an extra photo to every survey that includes a photo of an actual tag with that ID# precisely to avoid the issues you all were talking about of incorrectly inputting data in a previous question and associating all of that forms data with the incorrect tree.
That being said, because there are so many different projects with different needs is this something where a set of "best practices" could be published in documentation with examples of HIGHLY RECOMMENDED conventions/combinations of photo timestamp and UUID and then examples where users could add additional variables to the name with a very large WARNING about how edits to form data would create mismatches in file names?
I think what @Lloyd_Banwart said regarding large scale data collection is very much true and that ultimately a single solution for large scale projects will be disadvantageous for small scale projects and vice versa. Therefore, letting form creators choose form variables (in addition to photo timestamp and UUID) will create the possibility for the most meaningful and accurate file names, but also create the high probability that some form creators are going to have meaningful, yet inaccurate file names.
Tyler