You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not really. The main challenge with this, as I remember back when I implemented the new library, is how to represent all these tags in a data structure. This gets incredible confusing when you start looking into it; grouping the tags by their source (EXIF, XMP, IPTC) may be fine in Adobe Lightroom, but I'm not sure it's very user friendly from Hugo (the same tag may be placed differently depending on the photo editor used) ... But as I said, I have not thought about this lately.
I fully get your point. It really gets complicated if you think about it.
I thought maybe we could do some sort of guessing logic (for the most-used properties) and include a raw section so the user can, if they want to, fall back to it. But I’m not sure if a guessing logic of any sort is a good idea. You could do something like checking EXIF first and if null, checking IPTC and if that’s also null, taking the XMP property. But this could get a bit confusing if there are different values set in those sources. If well-documented and communicated, though, this might be a reasonable compromise.
Hej. First of all thanks for this amazing project!
As said in #12651 the new metadata package supports XMP and IPTC metadata. Would be really nice to have this feature therefore I created this issue.
Is there any update / plan on this topic?
The text was updated successfully, but these errors were encountered: