PDFlib TET PDF IFilter 4.0 Manual

Registered properties must not conflict in GUID+ID or name with existing Windows
properties (including the shell properties listed in Appendix A, »Predefined Metadata
Properties«). A list of Windows properties can be found at
msdn.microsoft.com/en-us/library/bb763010(VS.85).aspx
> You need proper privileges to write into the HKEY_LOCAL_MACHINE registry hive to
run the registerpropdesc tool.
> Since the registry stores only the name of the property description file (but not its
contents), the propdesc file must remain at the registered location to make sure that
the property descriptions will be available for searches.
> The propdesc file must be readable for all users.
> You can register multiple property files. However, two property description files
must not include descriptions of the same property (as characterized by GUID+ID).
Use the -u option to remove a previously registered property description:
registerpropdesc -u "c:\property\acme.propdesc"
Search for metadata properties. Once you configured custom metadata properties,
you can search for properties. Table 3.4 contains examples for property queries. The
names of all predefined properties for Windows Search are listed in Appendix A, »Predefined
Metadata Properties«. The syntax description for property-based queries can be
found at
www.microsoft.com/windows/desktopsearch/addresources/advanced.mspx
Shell properties can be queried interactively according to the samples shown in Table
1.1. Unfortunately, the Advanced Query Syntax for interactive searches does not support
custom properties in Windows XP/Vista, but only in Windows 7. In Windows XP/Vista
you must index metadata properties as text (see Section 3.6, »Indexing Metadata Properties
as Text«, page 45) in order to include custom metadata in interactive searches, or
use SQL-based searches (see below).
Table 3.4 Metadata query examples for Windows Search 3.0 and above
Search term example
author:Doyle
author:"Conan Doyle"
author:Doy
size: < 500000
date: