PDFlib TET PDF IFilter 4.0 Manual

3.8 Metadata in SharePoint and Search Server
Metadata property handling in Search Server is almost identical to metadata handling
in SharePoint. This section covers configuration steps for both products. In a few cases
product-specific details are mentioned explicitly.
You can programmatically control metadata handling in SharePoint using the Enterprise
Search Administration namespace Microsoft.Office.Server.Search.Administration. The
following concepts are used for handling metadata properties in SharePoint:
> Crawled properties are created by TET PDF IFilter when indexing (crawling) PDF documents.
Crawled properties can have multiple values. They are controlled via the TET
PDF IFilter configuration file. Sharepoint will search crawled properties like other
fields, but advanced features for property queries are not be available.
> Managed properties can be used in search queries and advanced search, and displayed
in search results.
More details on managed properties in the Advanced Search Page can be found at
msdn.microsoft.com/en-us/library/bb428648.aspx
msdn.microsoft.com/en-us/library/bb608302.aspx
XML configuration for TET PDF IFilter use with SharePoint. Table 3.5 lists requirements
and recommendations related to the XML configuration for TET PDF IFilter when working
with SharePoint.
Table 3.5 XML configuration for SharePoint
element attribute requirements and recommendation
Filtering useIdentifier Set to false to force GUID+name treatment of all properties including the
predefined properties.
Property emitAsVector Must be true for properties which may have multiple values (see Section
3.5, »Multivalued Properties«, page 44).
Property friendlyName Since GUID+name treatment facilitates locating properties in the list, we
recommend the use of this attribute (see »Property identification and
GUIDs«, page 40).
Configure custom metadata properties. Proceed as follows to prepare custom metadata
properties for indexing:
> Run a full crawl. During the crawl TET PDF IFilter will report the properties which are
configured in the XML configuration file and found in one or more documents. This
is required for SharePoint to pick up the newly found crawled properties.
> SharePoint will generate synthetic names (e.g. »Category 1«, »Category 2«, etc.) for all
new property categories. A PowerShell script which is installed with TET PDF IFilter
will create a list of category names and the corresponding GUIDs. Run the script as
follows:
list_categories.ps1
In the resulting list output you can identify categories via their GUID; compare the
GUID to those in PropertySet/@guid in the XML configuration file for TET PDF IFilter
(if you created custom properties) or the property set GUIDs in Appendix A, »Pre-
3.8 Metadata in SharePoint and Search Server 53