Properties in SharePoint Search

Most users of SharePoint Portal Server quickly become enamored with the ability to add new fields (with metadata) to documents in the document library. Suddenly it becomes possible to associate information to a file beyond the file name to us from the beginning limited to the computer age.
Few users, however, have the opportunity to understand how this meta data is used by SharePoint to search. This leads to problems when the user decides it is necessary to use SharePoint Portal Server Search to search the information in a field that had been added. In this article we will learn how SharePoint uses document library fields to create properties that can look and how to enable searching on those properties.

Power of Properties

Search SharePoint Portal Server is actually working in two different ways. First, is the full-text search. This searches through all the text in each document found in the index. This finding is most people think of when thinking about the search capabilities of SharePoint.
Second, is the search feature. During the indexing process, the IFilters to extract the text of the documents, put the information into segments that particular property ownership are held separately in the index so it can be searched separately. This allows you to set the properties of their Office documents, such as department, project number, author, keywords, etc, and then have the ability to search individual fields.



You can use the SharePoint search engine to search for documents in the engineering department and the project is 123. When a document search full-text engineering and 123 tickets are hundreds of words for engineering and 123 series appears in many documents, a search through the properties can give 10 or so documents that are actually relevant to your search.

Office Does a Slight of Hand

During the editing process, however, the Office is a slight bit of hand. We take the information you enter in the metadata fields of the document library and makes custom properties for the document. The net effect is that although only created the fields in a document library, documents now have custom properties.
These custom properties are picked up by the indexing process (specifically, the IFilter for Office documents) and placed in the search index. You can then use the properties of the provision through the advanced search page in SharePoint.But this also means that Office documents do not share the same relationship between the fields of the document library and the properties of each document. So if you're trying to develop a document search mechanism, such as TIF or PDF documents, you will find that the creation of a metadata field for the document libraries will not let you search for those documents directly through their properties. You will still be able to organize information