You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2026/08/22 00:16:00 UTC

[jira] [Resolved] (TIKA-4773) Expose all parsed XMP properties from images

     [ https://issues.apache.org/jira/browse/TIKA-4773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Allison resolved TIKA-4773.
-------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

> 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
>             Fix For: 4.0.0
>
>
> 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)