[
https://issues.apache.org/jira/browse/SIS-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Desruisseaux closed SIS-164.
-----------------------------------
Resolution: Not A Problem
Assignee: Martin Desruisseaux
The relationship between Tika and SIS is rather the other way around: SIS can
be one source of metadata (among many others) for Tika, while Tika is not a
source of geospatial data for SIS (Tika itself relies on other libraries for
geospatial data).
> Create a "sis-tika" module
> --------------------------
>
> Key: SIS-164
> URL: https://issues.apache.org/jira/browse/SIS-164
> Project: Spatial Information Systems
> Issue Type: Task
> Components: Metadata
> Reporter: Martin Desruisseaux
> Assignee: Martin Desruisseaux
> Priority: Major
>
> Creates a {{sis-tika}} module as a bridge between Apache SIS and Apache Tika.
> Tika is a generalized content detection and analysis library. One of its key
> components is a generic metadata container, that is typed. Tika can work
> before Lucene in order to represents data from various sources (PDF, Office,
> TIFF, etc.) in a uniform way that Lucene can index, but isn't dependent on
> Lucene.
> The most obvious SIS parts that can be linked to Tika are the
> {{org.apache.sis.metadata.iso}} packages. This SIS metadata module addresses
> specifically the ISO 19115 metadata, while Tika is more generic. Consequently
> we should be able to map all SIS metadata to Tika, but the converse may not
> be always possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
