Benson Miller
Guest
|
 Posted:
Tue Nov 01, 2005 9:51 pm Post subject:
Custom metadata available for searching? |
|
|
** This was also posted in microsoft.public.sharepoint.portalserver, but no
responses there so I'm expanding the audience. **
I am working on a SPS 2003 metadata indexing and searching solution for a
large PDF document store. I am using the PDF+ iFilter from ifiltershop in
conjunction with the free Adobe PDF iFilter.
I have assigned metadata to a test document. I can view the metadata through
Acrobat 7.0 Professional. I can also validate that the PDF+ iFilter is
appropriately exposing this metadata by using the FiltDump.exe utility
included in the MS Platform SDK. The only thing I'm missing is that
SharePoint does not seem to be registering this metadata when indexing runs.
When I browse to 'Manage properties of crawled documents', my custom
properties are absolutley not listed in /any/ of the property sets (hidden
or not). Given that the iFilter is exposing the metadata as expected, I
cannot understand why SharePoint does not include the properties in the list
of properties discovered in crawled documents.
Now, the PDF+ iFilter exposes custom metadata under a unique (generated by
me, using GuidGen.exe) property set GUID. I don't know whether this has any
effect on whether SPS will 'notice' this metadata and make it available for
management. My assumption was that any property set should be exposed by SPS
for management after an indexing run. My assumption seems to be incorrect.
Can anyone point me in the right direction? Are there registry keys that
effect this behavior? Other settings that are hidden in dark alleys?
Suggestions of more appropriate news groups for this query?
With appreciation,
Benson
* My email address needs modification for successful replies. * |
|
Benson Miller
Guest
|
| Posted:
Wed Nov 02, 2005 9:51 pm Post subject:
Re: Custom metadata available for searching? |
|
|
I find the lack of information on this topic disheartening. I have seen
other similar questions floating about the web, none of which has had a
single response.
In short:
My experience has lead me to believe that SharePoint will ignore custom
metadata that is exposed by the PDF+ iFilter. At any rate, the metadata that
is exposed by the iFilter is not available for managment through the "Manage
Properties of Crawled Documents" interface. This is not true for Office
documents, but it is empirically true of PDF docs (and perhaps all
non-Office documents).
I imagine that there must be some way to convince the indexing service to
consider the custom properties that I'm exposing. After all, I know (and
control) all defining characteristics of the property sets and associated
properties. If this is impossible, I will find it hard to interpret as
anything other than antagonism to other (non-MS) document formats.
Will anyone provide some guidance?
Regards,
Benson
"Benson Miller" <benson@NOSPAMspeakeasy.net> wrote in message
news:LfKdnX2wUuyDfPreRVn-vw@speakeasy.net...
| Quote: | ** This was also posted in microsoft.public.sharepoint.portalserver, but
no responses there so I'm expanding the audience. **
I am working on a SPS 2003 metadata indexing and searching solution for a
large PDF document store. I am using the PDF+ iFilter from ifiltershop in
conjunction with the free Adobe PDF iFilter.
I have assigned metadata to a test document. I can view the metadata
through Acrobat 7.0 Professional. I can also validate that the PDF+
iFilter is appropriately exposing this metadata by using the FiltDump.exe
utility included in the MS Platform SDK. The only thing I'm missing is
that SharePoint does not seem to be registering this metadata when
indexing runs. When I browse to 'Manage properties of crawled documents',
my custom properties are absolutley not listed in /any/ of the property
sets (hidden or not). Given that the iFilter is exposing the metadata as
expected, I cannot understand why SharePoint does not include the
properties in the list of properties discovered in crawled documents.
Now, the PDF+ iFilter exposes custom metadata under a unique (generated by
me, using GuidGen.exe) property set GUID. I don't know whether this has
any effect on whether SPS will 'notice' this metadata and make it
available for management. My assumption was that any property set should
be exposed by SPS for management after an indexing run. My assumption
seems to be incorrect.
Can anyone point me in the right direction? Are there registry keys that
effect this behavior? Other settings that are hidden in dark alleys?
Suggestions of more appropriate news groups for this query?
With appreciation,
Benson
* My email address needs modification for successful replies. *
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in