You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tyler Palsulich (JIRA)" <ji...@apache.org> on 2015/03/01 23:23:05 UTC
[jira] [Commented] (TIKA-675) PackageExtractor should track names
of recursively nested resources
[ https://issues.apache.org/jira/browse/TIKA-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342507#comment-14342507 ]
Tyler Palsulich commented on TIKA-675:
--------------------------------------
Is this still worth implementing? [~gagravarr], if you decide on metadata keys, I can take a crack at implementing this. But, not sure it'd be quick.
> PackageExtractor should track names of recursively nested resources
> -------------------------------------------------------------------
>
> Key: TIKA-675
> URL: https://issues.apache.org/jira/browse/TIKA-675
> Project: Tika
> Issue Type: Improvement
> Components: parser
> Affects Versions: 0.10
> Reporter: Andrzej Bialecki
>
> When parsing archive formats the hierarchy of names is not tracked, only the current embedded component's name is preserved under Metadata.RESOURCE_NAME_KEY. In a way similar to the VFS model it would be nice to build pseudo-urls for nested resources. In case of Tika API that uses streams this could look like {code}tar:gz:stream://example.tar.gz!/example.tar!/example.html{code} ...or otherwise track the parent-child relationship - e.g. some applications need this information to indicate what composite documents to delete from the index after a container archive has been deleted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)