Started by dcb, August 04, 2013, 05:14:01 AM
QuoteThe date is unknown. You have no idea at all other than knowing it was after the invention of the camera!
Quote from: Richard on August 04, 2013, 07:35:41 AMEntering estimated dates in IMatch has always been a pita but I developed my own work around.
Quote from: Mario on August 04, 2013, 09:57:06 AMWell, in fact the timeline is able to handle arbitrary groups of files. It's a matter of how the files are processing on import and how the individual nodes in the timeline are created. The current time line has been designed to work for standard dates using in archiving and imaging. For images it uses one of the three EXIF timestamps, for other file formats it uses other date information.
Quote from: Mario on August 04, 2013, 09:57:06 AMXMP and (with limits) IPTC and EXIF support incomplete dates, e.g. a date consisting only of the year. But supporting this makes things so complicated on so many levels (starting with ExifTool which does not support them) to all standard Windows calendar functions, comparison routines for dates, sorting by dates, all that becomes more complicated or has to be developed from scratch in order to handle situations where files with full dates and partial dates are to be processed in the same context.
Quote from: Mario on August 04, 2013, 09:57:06 AMAnd, based on experience, the majority of users only ever works with complete dates. For scanned photos, it is fairly easy to add a date and time original / digitized / created either with the built-in functionality in IMatch, the scanner software or ExifTool. This will then arrange the files properly in the time line. For other cases you can usually use something like 1.1.1900 or (1900) or 1.6.1900 (second half of 1900) to produce a complete date. For the purpose of including these files in the IMatch timeline this is usually sufficient. You can further mark these photos with a keyword, comment, Attribute, dot, pin, bookmark, flag or a special XMP label to make it easy to find and identify photos with uncertain dates.
QuoteRichard, what was your work-around?
Quote from: dcb on August 04, 2013, 05:14:01 AM...Further searches led me to the Library of Congress Extended Date/Time Format (draft) or EDTF for short. This I do like because it extends on ISO 8601 standard quite well.Under this approach, photos of a formal school ball that I know were from my late school years can be marked as 1987-11~ (Approximately Nov 1987). A photo from Christmas morning where the year is totally unknown could be uuuu-12-25. If I know it to be in the early 2000's (from memory) I might write 200u-12-25. Then as I honed in on a date it might become 2004-12-25~ (Approx 2004)...Place the EDTF date in the comment field (I still want a better field for this)...There will never be a right or wrong way to do this. What works for you, works for you. I hope this will help you find what that is.-David
Quote from: jch2103 on August 04, 2013, 11:51:45 PMBe sure to post if you figure out a better field to store EDTF data in. Maybe you can create a standard for IM5 users to follow...
QuoteI built categories decade.year.month...I have location.continent.country.state.city.sublocation categories