|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (4)
View Page History
...
The document repository stores and indexes annotated documents. It provides keyword search, facet search and analysis, and combined search. You can use the search capabilities either through the user interface, or through the API. {column}
{column:width=50%}
{column:width=50%}
{note} It is recommended that you select a value for the {{DOCUMENT_REPOSITORY_TYPE}} before you import any document into KIM 3.56. Changing the document repository afterwards will NOT transfer the previously imported documents to the new repository. However, the previously imported documents will not be deleted either, so you can switch back to the old repository in future.{note}
{column}
{section}
||Values||Description||
|{{lucene}}| stores the complete text of the documents and their annotations in an [Apache Lucene|http://lucene.apache.org/java] index. This document repository provides full-text search capabilities. This is the recommended and default option.|
{section}
||Values||Description||
|{{lucene}}| stores the complete text of the documents and their annotations in an [Apache Lucene|http://lucene.apache.org/java] index. This document repository provides full-text search capabilities. This is the recommended and default option.|
|{{only-store}}| stores the annotated documents as GATE XML files without indexing. Selecting a {{CORE_INDEX_ADDON}} is, thus, required for searching. This option is highly recommended if your application, based on the KIM 3.56, doesn't require full-text searching in the body of the document. In that case, selecting {{only-store}} will increase performance and decrease storage requirements significantly.|
|{{mimir}}| (*experimental*) stores the complete text of the documents and their annotations in [Ontotext Mimir|http://ontotext.com/mimir]. In addition to a full-text index, Mimir enables searching for annotation patterns. |
|{{sar}} | (*experimental*) stores the text and the annotations of the document in the embedded OWLIM SE as RDF using the KM module scheme of the [PROTON ontology|http://proton.semanticweb.org/] . This document repository provides full-text search capabilities. Enabling the {{sar}} index requires additional configuration. Please contact [support|http://ontotext.com/kim/support.html] for assistance if you intend to use the Semantic Annotation Repository (SAR).|
|{{sar}} | (*experimental*) stores the text and the annotations of the document in the embedded OWLIM SE as RDF using the KM module scheme of the [PROTON ontology|http://proton.semanticweb.org/] . This document repository provides full-text search capabilities. Enabling the {{sar}} index requires additional configuration. Please contact [support|http://ontotext.com/kim/support.html] for assistance if you intend to use the Semantic Annotation Repository (SAR).|
...||Possible values||Description||
|{{gate-xml}}| stores files as GATE XML documents. They can be opened with GATE Developer directly or imported into GATE Teamware.|
|{{gate-xml}}| stores files as GATE XML documents. They can be opened with GATE Developer directly or imported into GATE Teamware.|
|{{compressed-xml}}| stores files as GATE XML documents, compressed using [Glassfish XML Fast Infoset encoding|http://fi.java.net/] and then GZIP. Storage requirements are very low in this case, but the files need to be decompressed before use outside KIM 3.56.|
|{{simple-gzip}}| stores files as GATE XML document, compressed using the gzip compression algorithm.|
|{{xces-xml}}| stores files as [XCES|http://www.xces.org/] XML documents|
|{{xces-xml}}| stores files as [XCES|http://www.xces.org/] XML documents|
...h2. KIM Document Handlers
In KIM 3.56 we introduce new objects called document handlers. They are attached to the Document Repository module and are executed:
* before a document is added - one can add various features to the document or use to gain statistics
* after a document is added - mainly for statistics, but may be used to generate a detailed log for that document
* after a document is added - mainly for statistics, but may be used to generate a detailed log for that document
...