Hot answers tagged enterprise-search
2
Html content is usually in the crawled property:
Property Set: 11280615-f653-448f-8ed8-2915008789f2
Variant type: 31
Name: html
(http://msdn.microsoft.com/en-us/library/ff795815.aspx)
You can also add a "Spy" stage to examine what crawled properties are available in the pipeline - and see if you can find the one with the correct content. Or enable ...
2
If you're using SharePoint 2010 then you shouldn't use the SQL syntax the keyword syntax is simple just use
site:mylibrary test
2
Two things, the start address for Profiles should be sps3://mysitehost. The permissions on the User Profile Service for the default crawl account has to be allowed to "Retrieve People Data for Search Crawlers". Go to Central Administration | Application Management | Manage Service Applications. Select the User Profile Service Application (don't click the ...
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
You need to setup the site collection's search settings (Site Actions -> Site Settings -> Search Settings). Enable custom scopes by pointing the site to your search center, and set the dropdown mode to enable those scopes to be used. Additionally, you should also point it to the applicable search results for your search center, so that when users perform a ...
2
Here is what you are looking for. I have used this when I had to recreate my search center and it worked like a charm:
http://sharepoint.jsturges.com/2012/02/update-search-center-for-all-sites-in-a-web-application/
All you basically do is save your new search center url in a variable and use that variable to set the url to all sites within a web app by ...
2
Yes, you have two options:
Use the already configured search index of Farm A (search federation)
Crawl Farm A from farm B
You can get more information about configuration here: http://technet.microsoft.com/en-us/library/jj219577.aspx#Section12
2
The Search Center is a dedicate site template, with its dedicated onet / webtemp entries & definition.
You could easily add one to your site collection by creating a subsite with the template SRCHCENTERLITE#0 / SRCHCENTERLITE#1 or SRCHCEN#0.
Alternatively, you could inject the key search webpart within a dedicated page like in your code sample. You'll ...
2
This is NOT possible with Managed Property keyword queries. The only wildcard capability that Sharepoint Search Server 2010 supports is "Stemming". Stemming expects the characters to be matched by the characters at the start of a string in the index.
e.g. Item contains Title string "TestMe"
You're query can be : Title:"Tes" and that would pick up the ...
1
The issue seemed to be down to the size of the Index Partition. We reduced the number of items in the index using crawl rules and were able to get it down to about 8 million items from 12 million.
We were able to then make changes to the search topology.
What was interesting was the SharePoint Search Service on the rogue Crawl server would take about 90 ...
1
Crawler's have schedule to crawl, they don't just randomly start crawling, and it time depends on how you configured crawler's Schedule. You can check when your crawler crawled last time through Central Admin.
In the Search service application, you can schedule a full or
incremental crawl of a content source. There are four types of
Schedules:
...
1
Your best approach is to get titles on those weird formats into a separate managed property. Then you can do word searches on that property in FQL with less chance of the query bombing.
It's all about term expansion in the search engine core and how many terms would match and how big(slow) will the end query be.
The other approach is to create a full text ...
1
The scope of the rule:
If you define them in the search service, its valid for all
webapplications associated with that search service.
If you define it on subsite/web level, its valid for the contextual
search made on that site.
If you define it on site collection its
valid for the site and all subsites.
1
Do you have the site collection on the same physical server as your Central Administration / Search Service? If so, I had an issue similar to yours but the error was different. It had to do something with the search service being on the same machine as my site collections. After doing some research, someone mentioned this KB article:
You receive error ...
1
I think the portal.. part isn't correct and try specifying a column for the freetext predicate like this:
SELECT Title,ContentType,Path FROM SCOPE() WHERE FREETEXT(DefaultProperties,'samochód') AND (CONTAINS(Path,'"/BW/Lists/Pytania Bazy Wiedzy"'))
1
jack,
in order to use custom scopes instead of contextual scopes in result page we will replace Default Search Result Page with Search Site Result Page.
The following steps should be accomplished:
A. Create site or site collection for Search using one of the following site templates:
Enterprise Search Center
Basic Search Center
B. Enable to use ...
1
You are probably going to want to override the search box delegate control
Here is a nice overview of delegate controls
And here is someone overriding the search delegate control with a custom control
Instead of a creating the custom control like in the the second link, it sounds like you want to point your delegate control at the enterprise search bar ...
1
I can't think of an efficient way of doing this apart from tagging all documents.
The simplest and probably most efficient solution I can think of is, to do this on an event receiver when a document is added to the library, then writing an update script to set all the values of anything updated previously.
You could do this in a good afternoon and have it ...
1
If you're using standard SharePoint search pages, then you'll automatically get that passed to your KB article page.
HttpContext.Current.Request.UrlReferrer contains the full URL of the page which referred to the current one including QueryString.
So in a control on the KB article page you'll be able to check the UrlReferrer to check if it was a search ...
1
Here's a couple of quick ways to pass the query text to the result page:
Append the query text to each search result hyperlink url as a query string parameter
Add an onclick event handler to each search result hyperlink and save the query text to a cookie
You can accomplish each of the above by using jQuery or by editing the search results web part XSLT.
...
1
You need to create your own SearchResult web part which inherits from CoreResultsWebPart and assigns the value selected (probably transferred through QueryString in URL) to ResultsPerPage
There is a Results Per Page Search Core Results Web Part on Codeplex which you may be able to use
1
SharePoint sees the period as a word breaker (which means it treats each section of the IP Address as a separate word in the index and does not put them together). The only way to modify how SharePoint treats word breakers is with a custom dictionary: http://technet.microsoft.com/en-us/library/cc263242.aspx
1
Not out of the box, no. But that would not be too hard to create yourself.
Add a custom web part with a drop down for your page size options. You could even do this with SharePoint designer I guess.
When the user changes the dropdown value, reload the page and append something like ?pagesize=50 to the URL
Use the parameter for the pagesize property of ...
1
First, make sure that Search Service App and related accounts have "full read" permission with proper configuration on the site & document library content (as described here).
Document sets share common metadata amongst the documents in the container and there are no limitations (for crawling, document types, etc). After a search crawl, in the Search ...
1
In my experience is only related to Best Bets. Not sure about Fast, as there as some improvements related to visual best bests, but cannot imagine the behavior as different.
I believe you might have this http://technet.microsoft.com/en-us/library/hh133422.aspx
C:\Marius
1
I think that is not possible - you would have to implement a custom ranking layer between search and the search result webpart for the sorting.
I would not recommend this for an enterprise - for a custom, specialized searchsite with limited queries it would be an option.
Hope it helps!
Max
1
It will be hard to answer you like that, with so few informations.
Please could you log in the central administration, and control that the SharePoint Server Search service is started on the server, if not activate it.
Then, control that you have a running Search Service Application in the Service Applications.
If all these points are ok, try to control ...
1
I believe that the data that you get from crawled property is IEnumerable. So, I wonder that how you convert it into byte[] and then string?
I have tried this with no success because the "invalid character in a Base-64" is retuned.
XDocument inputDoc = XDocument.Load(args[0]);
var data = from cp in inputDoc.Descendants("CrawledProperty")
...
1
I looked at something very similar to this a long time ago, though did not end up implementing it. Our conclusion was the same as yours - a custom Protocol Handler was the way to go. I would recommend the Tisseghem/Fastrup book too.
Note that writing one is fairly involved looking, and seems to be often done in C++.
1
I think it is related to the ErrorDeleteCountAllowed and ErrorDeleteIntervalAllowed of the crawl deletion policies.
More detail here: http://blogs.technet.com/b/tothesharepoint/archive/2011/01/20/managing-crawl-deletion-policies-for-sharepoint-server-2010.aspx
Only top voted, non community-wiki answers of a minimum length are eligible
