[
https://issues.apache.org/jira/browse/TIKA-3789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-3789:
------------------------------
Description:
There are some use cases where custom parsers might want to pass metadata from
embedded files to the parent's metadata in the /tika (json) output or
programmatically.
We can follow the pattern in TIKA-3788.
As with TIKA-3788, this metadata will be written after the parse so it will not
show up in standard xhtml output (e.g. /tika (html/xhtml) or programmatically
in the XHTMLContentHandler). However, it will appear in the json output option
from /tika and in the Metadata object programmatically.
As with TIKA-3788, we encourage using the /rmeta endpoint, -J in tika-app or
the RecursiveParserWrapper instead of this option. However, for those who need
to work with a flattened view of a document, this can be invaluable.
was:
There are some use cases where custom parsers might want to pass metadata from
embedded files to the parent's metadata in the /tika (json) output or
programmatically.
We can follow the pattern in TIKA-3788.
As with TIKA-3788, this metadata will be written after the parse so it will not
show up in standard xhtml output (e.g. /tika (html/xhtml) or programmatically
in the XHTMLContentHandler). However, it will appear in the json output option
from /tika and in the Metadata object programmatically.
> Allow parsers to pass embedded metadata to container file's metadata
> --------------------------------------------------------------------
>
> Key: TIKA-3789
> URL: https://issues.apache.org/jira/browse/TIKA-3789
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Priority: Minor
>
> There are some use cases where custom parsers might want to pass metadata
> from embedded files to the parent's metadata in the /tika (json) output or
> programmatically.
> We can follow the pattern in TIKA-3788.
> As with TIKA-3788, this metadata will be written after the parse so it will
> not show up in standard xhtml output (e.g. /tika (html/xhtml) or
> programmatically in the XHTMLContentHandler). However, it will appear in the
> json output option from /tika and in the Metadata object programmatically.
> As with TIKA-3788, we encourage using the /rmeta endpoint, -J in tika-app or
> the RecursiveParserWrapper instead of this option. However, for those who
> need to work with a flattened view of a document, this can be invaluable.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
