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 2016/03/07 16:27:40 UTC
[jira] [Commented] (TIKA-1894) Add XMPMM metadata extraction to
JempboxExtractor
[ https://issues.apache.org/jira/browse/TIKA-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15183137#comment-15183137 ]
Tim Allison commented on TIKA-1894:
-----------------------------------
Update made to trunk with commit c5d4ec6c50824a9a40fdd2b492bf7557d8d693f3.
In 2.0, I'm not sure how to share JempboxExtractor with the multi-media-module and the pdf-module. As expected, we get a cyclic dependency error if I add the multi-media-module as a dependency to the pdf-module, and, even if it did work, that wasn't a good option.
Some options:
#. Create a tika-parser-xmp-module that would include helper functionality for extracting xmp packets & metadata. Is this enough to warrant a separate module?
#. Duplicate code (no!!!).
#. Other options?
> Add XMPMM metadata extraction to JempboxExtractor
> -------------------------------------------------
>
> Key: TIKA-1894
> URL: https://issues.apache.org/jira/browse/TIKA-1894
> Project: Tika
> Issue Type: New Feature
> Reporter: Tim Allison
> Priority: Minor
>
> The XMP Media Management (XMPMM) section of xmp carries some useful information. We currently have keys for many of the important attributes in tika-core's o.a.t.metadata.XMPMM, and JempBox extracts the XMPMM schema, but the wiring between the two has not yet been installed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)