dschmidt opened a new pull request, #2927: URL: https://github.com/apache/tika/pull/2927
Metadata Extractor parses the whole XMP packet, but the image extractor only copies the Dublin Core and XMP-MM schemas into the metadata. Everything else is parsed and then dropped, including vendor namespaces such as the ones Google Motion Photos use. This adds a handler that copies all parsed XMP properties (keyed by their `prefix:name` path) and skips keys that already map to a known Tika field, so normalized values are not shadowed. It also pre-registers canonical prefixes for the Google photo namespaces. XMPCore's namespace registry is process-global and keeps whichever prefix the first parsed file declares for a URI, so the same namespace can otherwise surface as `Camera` or `GCamera` depending on parse order; pinning the prefixes keeps the keys stable. Example output for a Motion Photo, alongside the usual EXIF: ``` Camera:MotionPhoto = 1 Camera:MotionPhotoVersion = 1 Camera:MotionPhotoPresentationTimestampUs = 500000 Container:Directory[2]/Item:Semantic = MotionPhoto Container:Directory[2]/Item:Length = 122562 ``` Tests cover both the current Motion Photo format and the legacy MicroVideo format, using small synthetic files. `mvn clean install` for `tika-parser-image-module` passes (checkstyle, forbidden-apis, RAT, and the full test suite). Note: I do not have an Apache JIRA account yet (requested). I will add the `TIKA-XXXX` id to the title and commit message once the issue is filed; opening now for early feedback. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
