I appreciate your response.
I completely understand the concepts / impact of industry-standards vs Mylio-proprietary features. Certainly any user or system using a standard field in a non-standard way is taking risks. But lack of a standard does not mean “do nothing” or “support the feature halfway”.
Some things fully in Mylio’s control that can help the cause:
Provide an option / setting to erase date taken in the JPG when date taken in the tool is set to “Undated”. User takes the risk regarding how other tools deal with this.
Provide an option / setting to set a dummy date of the user’s choosing (e.g., 1/1/1800) to signify “undated”. Whenever the user clicks “Undated” that date is actually populated, rather than having to navigate the date picker.
Provide an option / setting for how to handle missing “date taken” when importing files, such as “Set to undated”, or “Use date modified”, or “Use date created”. Currently it is locked in on “Use date modified”.
Mylio already demonstrates some leadership by supporting “undated” within the tool. It could petition the governing bodies to address this at an industry level. Instead of viewing this as another support ticket, view it as an industry opportunity.
Mylio must first decide whether to make improvements in this regard, or continue as is (to only support “undated” within the tool) and communicate the decision. So far, the response has been along the lines of “that’s the way it is”, though I otherwise find the support extremely helpful.
If continuing as is, Mylio should at least provide a error message to the user as it does not truly “Save metadata to file” for undated photos.
For cataloging / archiving, the Mylio concept is the best I have found. Just like to see the execution match the concept. I hope that the needs those like me focused purely on cataloging / archiving, don’t get lost amongst the needs of professional photographers and others with “heavy duty” needs.
Sorry that was a bit long. BTW, responses to some of your comments/questions:
I’d guess you used the default Windows 10 “Scan” app.
I used Epson scan not a Windows tool.
“If I’m unsure of the exact date - I’ll set this to Jan 1st of the year I believe the pictures are from.”
I could probably do a workaround like this. Sometimes I have no idea of even the decade (was it the 1870s or 1880s?).
“Technically, There is no such value as “undated” for the
Date Taken EXIF field. “Undated” simply means that field is MISSING”.
Works for me if MISSING is interpreted by Mylio as “Undated”. As it stands, when Mylio imports a photo with a missing date taken, it maps the “date modified” (file) to “date taken” (Mylio).
“I guess you could make a case that if this field is missing, Mylio should not create it. But every other photo app on the planet is still going to create it & populate it with a date anyway.”
Other apps with use the JPG fields as they see fit, regardless of how it is handled by Mylio. In my case anyway, I use no tools for editing, etc. This is why perhaps Mylio can offer options for how “Save Metadata” is handled.