5 ms·
Hierarchies vs tags has come up for me in my recent effort to scan and organize thousands of old family photos (100+ years old). My main goal is to make the da
by asielen 5y ago
Hierarchies vs tags has come up for me in my recent effort to scan and organize thousands of old family photos (100+ years old).
My main goal is to make the data as future proof as possible, in my mind that means going with some standard filesystem hierarchies but supplementing it with photo metadata using exiftool. I don't trust any tagging solution to be useable in 5+ years that isn't based on EXIF/XMP standards and that only really works for photos (and not all formats). While you can force write XMP standard metadata onto unsupported file types--there is a push to standardize XMP across all files--metadata support is far from standard across operating systems or tools.
For my purposes I have a folders with Ahnentafel numbers so they can be quickly found: https://en.wikipedia.org/wiki/Ahnentafel https://en.wikipedia.org/wiki/Ahnentafel
I do my best to organize photos into the family/generation that is most represented by the photo and then into "events" if possible.
I then use lightroom to tag the photos with as much information that I can, especially the names of the people in the photos.
This way I figure, even the least technical person can find photos from a specific family but with slightly more effort, they can also search for people across the folder hierarchy.
- im3w1l 5y agoAs far as future proof goes, Danbooru has been on the web for 15 years and on github for 10 and is still actively developed. There is a web interface and also a webapi. But the (lack of) access control may be a problem. Maybe with appropriate nginx auth config you can ensure only the family can access it. If you search for it beware NSFW.
- ClumsyPilot 5y ago"I don't trust any tagging solution to be useable in 5+ years" Damn me, but this is true. Our industry is totally irresponsible and run by children.
- eredengrin 5y agoI've been meaning to try out PhotoStructure[1] for a while now as it looks like it might just be a good place to finally put some effort into organizing my collection. Nothing is guaranteed to last forever but it looks like the author is planning ahead in this case such that even if he goes out of business, all the work I put into organizing would not be meaningless (data is stored in a sqlite db and code will be open sourced in event of business closure). [1] https://photostructure.com/ https://photostructure.com/
- mceachen 5y agoHowdy! I'm the author of PhotoStructure. Hierarchical tags are fundamental to PhotoStructure! Read more here: https://photostructure.com/faq/whats-a-hierarchical-tag/ https://photostructure.com/faq/whats-a-hierarchical-tag/ Any change you make to your assets in the PhotoStructure UI is stored both in your library database as well as either within the file itself using standard EXIF/IPTC headers, or as a standard sidecar format (like .XMP or .MIE), to ensure your work isn't wasted if you migrate to another tool in the future. More details are here: https://photostructure.com/faq/system-of-record/ https://photostructure.com/faq/system-of-record/ I'm happy to field any questions about PhotoStructure or metadata Management in general, either on the forum or on discord (links on the website).