#390 - Add XMP namespace to embedded exif data #392
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #390
** Current behavior
Currently, namespaces in the file's embedded metadata other than EXIF are not processed and thus not available for generating albums when customizing album creation.
** Changes introduced by PR
Adds the XMP namespace to the EXIF data if (and only if) embedExif is true.
As an example use case, my filter.js which I'm using to produce albums based on the more structured hierarchical keywords used by Darktable and Digikam.
** Does it introduce a breaking change for existing users?
No, this should be completely transparent to existing users.