The Content By Type webpart allows searching for documents by adding different search filters, ie, to add and view the contents of a particular type of content (Content Type) from different sites.
This WebPart is developed by e-Office and can be obtained for free from the author's website author's blog .
To use Content Type By start by creating a Web site called SharePoint Server Search Test:
To try the search of documents, some documents inserted in the new web site created:
The next will either install the webpart By Content Type in the server. After copying the installation files on the server, run setup.exe:
The installer will take care of several automated tasks, freeing us to perform them manually:
However, in our case, we find an adverse circumstance that does not allow installation is complete, and the WSS Administration service is not started. We proceed therefore to the initiation of the service manual:
Once the service in question, you must restart the installation of Content By Type. On this occasion, all the initial checks are successful:
By Content Type
install web applications for all of our SharePoint Server:
After this, start the actual installation of Content By Type:
A report shows that Content By Type has been added successfully to selected web applications:
now within our website, search engine test, edit the main page:
We will have to select Add a Web Part:
As noted, the Content By Type webpart is listed as a type Miscellaneous. After that, is already our Content By Type webpart in the selected location, but initially did not offer the functionality to be set, for which we see a link about it:
After opening the toolpane of the webpart, we get a configuration panel where you specify the following options:
After deploying the advanced options, specify the following values:
After that, we open the editor configuration, which specify the following settings:
Once done, we have the Content By Type webpart configured:
However, we can see how we asks you to associate a filter to perform a search. If we had left the property off Just query on filter appear to us the result of a search that would return all elements of the data source. However, if we have the ability to filter, we begin by adding a new filter (within the Add a Web Part):
In our case, we will add a text filter that the user can filter by file name:
Then we connect the filter Filename "with the webpart" Search Records "
specify that the value of the filter text box is used to filter the search by the field name:
The result would be visible on the page as follows:
If you enter the value "Prueba3.docx" in the filter text box we have created and press the enter key, we get the following result:
If we try use the * wildcard character in the same way we got used MS-DOS, we note that is not recognized as such, but literally as a wildcard:
If we try to search for documents which have not been "checked in", will not be returned in our searches:
To address this, we "check in" on the document in question:
Now the document is accessible by Content By Type:
Now let's test the feasibility of nested filters so that a search criterion contemplated as a result of nest various filters. To do this, we add a new text filter in order to filter by the document's title:
We
to check the results. For this reason, before we assign the title "Document 7" to file named "Doc 7.docx." If we look for the documents named "Doc 8.docx" and get the file empty title "Doc 8.docx"
If we change the title of the filter to "Document 7" and maintain the value "Doc 8.docx" as filename to search, we do not get results. This proves that the two filters are run concurrently on the search:
Finally, we tried to search for entitled "Document 7" filename "7.docx Doc," which returns us the file "Doc 7.docx"
is also observed, which is it impossible to assign multiple filters to a single search field. If we add a new text filter, and assign the field name as the first filter to create, to perform searches and get an error that is displayed:
