Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XMP and IPTC image metadata support #13146

Open
LNA-DEV opened this issue Dec 14, 2024 · 2 comments
Open

XMP and IPTC image metadata support #13146

LNA-DEV opened this issue Dec 14, 2024 · 2 comments
Labels
Milestone

Comments

@LNA-DEV
Copy link

LNA-DEV commented Dec 14, 2024

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?

@bep
Copy link
Member

bep commented Dec 14, 2024

Is there any update / plan on this topic?

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.

@bep bep removed the NeedsTriage label Dec 14, 2024
@bep bep added this to the v0.140.0 milestone Dec 14, 2024
@LNA-DEV
Copy link
Author

LNA-DEV commented Dec 15, 2024

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.

But maybe you or someone else has a better idea^^

Anyway, I’m looking forward to it 😄

@bep bep modified the milestones: v0.140.0, Unscheduled Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants