Hot answers tagged search-results
6
The problem i've encountered was linked to the reference i was using.. I used
Microsoft.SharePoint.Search.Query
instead of
Microsoft.Office.Server.Search.Query
In the version i was using it was impossibile to query sharepoint giving him parameters and so on... But the firm of every class and method was the same..
Now it works!
Thanks to all!
5
You also need to install the iFilter from Adobe in order to allow SharePoint to index the PDFs. The configuration changes you made simply tells SharePoint to index PDF, but the iFilter is actually what does the work.
Start here: http://support.microsoft.com/kb/2293357
4
When properly configured, the user's authorization is factored into search results in a process called Security Trimming. Here is a good TechNet article that provides an overview: http://technet.microsoft.com/en-us/library/cc263520(office.12).aspx
Here is some info on configuring search for MOSS 2007: ...
4
IMHO - I reproduced the issue you are having on one of our systems except for the use of Claims authentication. My search account does have 'Read' access for the web application. A list was created and anonymous access was initially enabled from inheritance. The search index was already built (it is scheduled to run often) and could query the list as ...
4
Keeping the structure as is I would go with a custom webpart (override the CoreResults web part) and do this as two queries, instead of a custom pipeline module.
First execute your main query, this will give you the id's for all your metadata. Then execute a second query where you retrieve all the list items and their columns in an OR query. No need to ...
4
I don't think you can get rid of the textbox.
But the other two requirements may be solved by modifying the Refinement Panels Filter Category Definition. Here is the valid option for the Refinement Panel XML Schema.
SortBy="Name" SortDirection="Descending" should give you the ordering you need.
MaxNumberOfFiltersToDisplay="50" ShowMoreLink="False" should ...
4
If you have a high ratio of queries compared to deletes, then you might want to add an event receiver which calls CrawlRuleCollection.RemoveFromResults upon deletion of an item
3
I'm guessing that Tag is a Managed metadata column? If so, doing an equals compare using Column = 'Value' won't work, as the actual text in the property could potentially hold more values, lookup value based managed metadata properties store the values differently in the index.
So you would have to use a CONTAINS or a LIKE. Any search using a lookup column ...
3
CoreResultsWebPart is not calling RenderContents so that's why it doesn't matter that you override that. You can override RenderWebPart, but I'd recommend to use XSLT, in ModifyXsltArgumentList you can add ExtensionObjects to do your lookup. (If it can take more than 1 second, then you need to apply February 2012 CU).
Another thing to consider is that if ...
3
Did you create the mapped property "Department" mentioned in the refinement panel? If not, create the mapped property and perform a full crawl again. Follow the instructions in this post which does the same.
Good Luck .
3
I think you'll need:
(ColName:Val1) AND (ColName:Val2)
Without the AND, yes, they are implicitly OR'd, as they're the same column. This is mentioned in the documentation, but it doesn't make it clear that you can explicitly AND them.
If the column names were different, they would be explicitly AND'd - but in exactly the same way you could explicitly OR ...
2
It's not a short or simple article but I think it applies to your issue:
Trim SharePoint Search Results for Better Security
Microsoft SharePoint search uses an account that usually has full read
access across the repository to index its contents. So it’s important
that when a user queries for some content, he should be restricted to
view only the ...
2
You'll need to use and IFilter to crawl the content of PDF-documents. It should work out of the box for Office-documents.
Here's a detailed tutorial (I haven't tried it)
2
Sharepoint search inherits from the same permission structure as other items. So that means; if an item is not viewable by a user, then it will not be available through this user's search also.
Results to be shown depends directly on the permissions of the items' permissions to be shown.
I guess you should do a re-crawl for the search, then observe the ...
2
Assuming that the Search is for SharePoint content (sites, lists or list items), the users in the group will not see the content in search results for which they don't have permissions. So you can fine tune the permissions on SharePoint content so that only authorized users see items in search results.
This kind of security-trimming is provided out-of-box ...
2
The SharePoint Search does something which is called Wordbreaking and Stemming. Means that words existing of 2 or more words (for example: housewife = house % wife) are broken and added to the index. If you then search for the whole word or a part of it you will get all the results. Stemming means that SharePoint tries to find variations of a word and adds ...
2
Replace your XSLT with the following piece of code (don't forget to backup ;))
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
<xsl:template match="/">
<xmp><xsl:copy-of select="*"/></xmp>
</xsl:template> ...
2
OTB Enterprise Search Center uses mimimal.master page which does NOT have all elements that your custom(or other OTB ) master page has. You have to develop a custom master page for search center or use your existing master page and make sure that they are compatible with search center controls and web parts.
Following links should help you get started:
...
2
QMKevin,
Maybe i found a solution:
In the refinement webpart, view this section:
> <Xsl> <?xml version="1.0" encoding="utf-8"?> <xsl:stylesheet
> version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> xmlns:ddwrt="http://schemas.microsoft.com/WebParts/v2/DataView/runtime"
> xmlns:ddwrt2="urn:frontpage:internal">
...
2
You can limit the search returns with the query you use, and not have to change the crawl rule.
For example, If you are searching for "Product", you can enter the following into the search query box:
Product IsDocument:1
and you should only get documents and not folders.
You can configure the query web part to automatically append IsDocument:1 to all ...
2
Here's a couple of options for you:
In Central Admin, go to your Search Service Application (Content SSA if you use FAST Search for SharePoint) then navigate to Server Name Mappings and create one. Set the "Address in index" field value to your Extended zone url (the one configured to be crawled in the content source) and set the "Address in search ...
2
SharePoint Server (or Search Server Express)
If running SharePoint Server (or Search Server Express) you can change the XSLT used to display the search results:
Go to the search result page
Put it in Edit mode
On the Search Core Result Web part select "Edit Web Part"
Open the Display Properties category
Deselect "Use Location Visualization"
Click XSL ...
2
Despite the Exception thrown the problem is a XSLT Extension method taking to long time to complete.
In SP2010 SP1 the SharePoint team introduced a check in the XsltTransformations done by Data Form WebPart and thereby in Search Core Results WebPart (as it inherit from that), that the latest entension method has to complete within 1 second of the first being ...
2
I've had a similar response here on stackexchange available here where using DVWp with the results coming from Search XML are then taken via SPD 2010 two column layout using XSLT of People Search Core Result WebPart
I found that SPD 2010 is an excellent tool for getting extremely quick customization, you can then use standard operations to group/sort, etc.
...
2
Out-of-the-box - just by using the User Interface (e.g. Web Parts) i don't believe is possible particularly for large result sets (you will always get a "estimative" count of RESULTS - see here for more details - http://blogs.msdn.com/b/sanjaynarang/archive/2009/02/20/handling-paging-and-total-results-count-in-sharepoint-custom-results-page.aspx).
On the ...
2
Yes, you will need to implement a custom solution to accomplish this. The OOTB results Web part is unfortunately hard-coded for sorting by relevance or modified date. This limitation is first removed with SharePoint 2013 Search where managed properties can now be registered as sortable.
In SharePoint 2007, you can implement custom sorting using the ...
2
You can try making a BDC Entity for your XML file and make External List for that... You can then use SharePoint Forms as well to manipulate data for your XML
You can deploy the XML file into Layouts folder somewhere and access it from there...
Then you can use Search with your External List or Configure Search for External Content Type
Too much I guess ...
2
I like the BDC route, however if you just want to get the data into SharePoint, use PowerShell to read the XML file and load it into a list.
See http://www.windowsitpro.com/article/powershell-faqs/Q-Can-PowerShell-read-and-parse-XML-files for a quick help on how to read an XML file. Then you could mimic this script, but instead of a Excel/CSV, use your XML ...
2
This is how we did something similar for our environment. On the master page or page layout you would create a declaration for this code and use a control to wrap anything you want to hide from the crawler.
Implementation and explanation from here: http://www.sharepointdesigners.net/profiles/blogs/sharepoint-search-partial-page-exclusion
was then ...
2
Sanghoon,
this message comes from resource file embedded into assembly
microsoft.office.server.search.intl.dll
and for Core Results web part this message renders when Query Error occurs instead of displaying actual search result, this is why for message XSLT customization could not be applied as for regular search results.
But it could be ...
Only top voted, non community-wiki answers of a minimum length are eligible
