[
https://issues.apache.org/jira/browse/TIKA-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18093970#comment-18093970
]
ASF GitHub Bot commented on TIKA-4773:
--------------------------------------
dschmidt commented on PR #2927:
URL: https://github.com/apache/tika/pull/2927#issuecomment-4891698554
Dunno, how you want to handle the Copilot review(s) - I think I addressed
all comments, but wanted to leave it up to you to resolve the conversations.
Good?
> Expose all parsed XMP properties from images
> --------------------------------------------
>
> Key: TIKA-4773
> URL: https://issues.apache.org/jira/browse/TIKA-4773
> Project: Tika
> Issue Type: Improvement
> Components: parser
> Affects Versions: 3.3.0
> Reporter: Dominik Schmidt
> Priority: Major
>
> The image parser uses Metadata Extractor, which parses the complete XMP
> packet,
> but ImageMetadataExtractor only copies the Dublin Core and XMP-MM schemas into
> the metadata (via JempboxExtractor). Properties from any other XMP namespace
> are
> parsed and then dropped, including vendor namespaces such as the ones Google
> Motion Photos use (Camera / Container / Item).
> As a result XMP that Tika already parsed is not exposed for image files.
> Proposal: copy the XMP properties that Metadata Extractor exposes via
> XmpDirectory.getXmpProperties() into the metadata, keyed by their prefix:name
> path, skipping keys that are already set or that match a known Tika field so
> normalized values are not overwritten.
> Also pre-register canonical prefixes for the Google photo namespaces, because
> XMPCore keeps a process-global URI to prefix registry and adopts whichever
> prefix
> the first parsed file declares; without pinning, the same namespace can
> surface
> as either "Camera" or "GCamera" depending on parse order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
