17.05.2014 Views

PDFlib TET PDF IFilter 4.0 Manual

PDFlib TET PDF IFilter 4.0 Manual

PDFlib TET PDF IFilter 4.0 Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3.10 Metadata in Indexing Service<br />

Create a column definition file. In order to use custom metadata properties with Indexing<br />

Service you must prepare a column definition file (often called msscolmn.txt)<br />

which specifies the names, data types, and GUIDs of properties. The property entries<br />

must match the corresponding property descriptions in the XML configuration file. Column<br />

definitions must be specified according to the following syntax:<br />

"FriendlyName" (Type) = PropertySetGuid PropertySpec<br />

Each line contains all or a subset of the following components:<br />

> FriendlyName (must be enclosed with double quotation marks): alias name for the<br />

property (must not contain whitespace): should match the name attribute of the<br />

Property element in the XML configuration file (or the name of one of the predefined<br />

properties listed in Appendix A, »Predefined Metadata Properties«)<br />

> Type (optional; must be enclosed with parentheses): must match the type attribute of<br />

the Property element in the XML configuration file, using the type designations<br />

shown in Table 3.9. If this entry is missing, the default type DBTYPE_WSTR | DBTYPE_<br />

BYREF (i.e. String) will be used.<br />

> PropertySetGuid: must match the guid attribute of the PropertySet element in the XML<br />

configuration file.<br />

> PropertySpec: must match the friendlyname attribute or the identifier attribute of the<br />

Property element in the XML configuration file. The friendlyname can only be used if<br />

the identifier attribute is missing or if the useIdentifier attribute of the Filtering element<br />

is false. The identifier can be specified in decimal or hexadecimal (starting with<br />

0x) notation.<br />

Empty lines and lines beginning with a number sign »#« will be ignored and can be<br />

used for comments. The following example demonstrates a few property descriptions<br />

(the first line with the [Names] entry is important):<br />

[Names]<br />

"fontcount" (DBTYPE_I4) = 5eac0060-1ba4-11dd-92c4-0002a5d5c51b 2<br />

"weblink" (DBTYPE_WSTR | DBTYPE_BYREF) = 5eac0060-1ba4-11dd-92c4-0002a5d5c51b 6<br />

Table 3.9 Property data types for Indexing Service<br />

data type in <strong>TET</strong> <strong>PDF</strong> <strong>IFilter</strong><br />

data type in property descriptions in<br />

mscolmn.txt<br />

data type for Indexing Service<br />

(interactive editing of properties)<br />

Int32 DBTYPE_I4 VT_I4<br />

Double DBTYPE_R8 VT_R8<br />

Boolean DBTYPE_BOOL VT_BOOL<br />

DateTime DBTYPE_DATE VT_DATE<br />

String<br />

DBTYPE_WSTR | DBTYPE_BYREF<br />

for properties with vector treatment:<br />

DBTYPE_WSTR | DBTYPE_VECTOR<br />

VT_LPWSTR<br />

Note Column definition files do not seem to work with 64-bit versions of Indexing Service.<br />

3.10 Metadata in Indexing Service 59

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!