PDFlib TET PDF IFilter 4.0 Manual
PDFlib TET PDF IFilter 4.0 Manual
PDFlib TET PDF IFilter 4.0 Manual
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Scenario 1: Transparently blend metadata properties into the main text. If metadata<br />
properties contains sufficiently distinctive text which identifies the target document(s),<br />
it will suffice to include the properties in the full-text index and include it in<br />
standard full-text queries. For example, if you query for a specific article number, it<br />
doesn’t matter whether the number occurs in the main text of the document or in a<br />
metadata property, as long as only one particular document talks about the article<br />
number in question. In other words, if it doesn’t matter whether the text occurs in the<br />
main text or some metadata property, you must simply enable the indexing of properties<br />
as full-text, without any additional steps.<br />
Use the following XML configuration to transparently blend metadata into the main<br />
text:<br />
<br />
Scenario 2: Distinguish metadata from the main text. In other situations it may be relevant<br />
whether the text occurs in the main document or in some metadata property. For<br />
example, it makes a big difference whether you search for documents authored by<br />
Doyle, or documents which include the term Doyle in the main text. In this scenario you<br />
must not only enable the indexing of properties as full-text, but also include suitable<br />
prefixes for each property which make it possible to distinguish between text in the<br />
main document contents and text in metadata properties.<br />
The value of the predefined property System.Author will be prepended by the prefix<br />
<strong>TET</strong>_System_Author_. For example, you can emulate a property-based search for<br />
System.Author=Doyle with a full-text search for <strong>TET</strong>_System_Author_Doyle. Since<br />
System.Author is a predefined property, the corresponding XML configuration does not<br />
require any property-specific entries, but must simply enable indexing of properties as<br />
prefixed text:<br />
<br />
In order to emulate a property-based search for documents with the article number<br />
XY123456 with a full-text search for ArticleNumber_XY123456 use the following XML configuration:<br />
<br />
<br />
<br />
<br />
<br />
<br />
46 Chapter 3: Metadata Properties
Change language