Hot answers tagged

8

Yes you need Office Web Apps to enable Document Preview. And Yes that needs a separate server/farm.


5

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 ...


5

Please refer to the following blog post which described basics of sharepoint 2013 ranking models. http://powersearching.wordpress.com/2013/03/29/how-sharepoint-2013-ranking-models-work/ Please let me know which model are you interested in, I will cover this in following posts.


4

XML files are searched and indexed natively in SharePoint 2010 using the out-of-the-box engine (FAST is just a search add-on/alternative but uses the native engine under the covers so it's a supplement and will search XML files using the native engine). It's a little confusing because you say you're using FAST (generally a product related to SharePoint ...


3

First of all you need to make sure that you have created a managed property from your crawled property. In addition make sure that it is also set up as a 'Refiner Property' as well in the managed property creation screen. Then do the following: Go the search results page and edit the refiner web part Make sure that the 'Use Default Configuration' check ...


3

By default the FAST would store index file(s) on file system and the location would be: [InstallPath]\Data\Data_index


3

We had a similar problem on extending CoreResultsWebpart, the problem was in .webpart file properties list, which lacked of some entries such as ScopeID, RelevanceView, etc. We updated the list (copying properties from the original webpart), re-deployed, removed and reinserted webpart on sharepoint page, and all went ok.


3

You can still use FAST ESP - which does not require SharePoint.


3

FAST cannot index user profiles. You need to configure enterprise search for this. Make sure User Profile Synchronization is running and you have profiles imported Give your search default content access account "Retrieve People Data for Search Crawlers" permission on User Profile Service Application Configure a new Content Source "People" that points to ...


3

If you change your code to use "yield return" you should give out id's as the crawler asks for it, instead of building up a long list internally which is then returned. I haven't tried this myself, but using yield is the perfect way to fetch data as needed. Could be worth a try. I suspect you can do something similar when it ask for each item, if you keep a ...


3

Your understanding is not correct. So rule, if a crawl is running and schedule for another crawl schedule (Lets say full) on the same content source is approached then running crawl always took the priority & continue. Now Full crawl will be skipped and wait for the next schedule which is next week in your case. If you don't want to overlap them then i ...


3

With KQL it is only possible to query by day ranges. If you want to use something like DateTime.Now you will have to use FQL instead, see link


2

You can check the Fast Search Server Version by In Control Panel, under Programs and Features, click "Microsoft FAST Search Server 2010 for SharePoint" and you will see the version number here as well.Also click on View installed updates to see all installed updates. Fast search server is seprate product then the Sharepoint, So SharePoint patches/Hotfix ...


2

The ModifiedBy column has to be accessed as 'Author', you don't have to specify a specific value as stated in the link you provided. To get ModifiedBy back, use Author.


2

According to msdn article you posted it looks like it is hard limit. Can you split long query into multiple smaller and merge results?


2

You can use Refinements to find all the possible values for Managed Properties. Refinements will also include the counts for each Managed Property. Look here for more details on how to configure: http://msdn.microsoft.com/en-us/library/ff394639%28v=office.14%29.aspx


2

As you have seen, the limit for the Query is actually 2048 characters. So any more than that will throw this exception. http://stackoverflow.com/questions/8061330/how-to-overcome-fast-search-char-limitation-2048 is a possible duplicate of your question, but sadly it never recieved any attention. Also this from Technet ...


2

This is not possible - the searchbox overrides the refinement. The idea behind it is: The end-user starts searching by using a phrase/keyword in the textbox - then he refines the result set with the refiners.


2

You have to use a pipeline extensibility stage which reads the text based property and writes it back to a new crawled property of type int, which you can map to an int based managed property. I've done the same for date <meta> tags in web pages which are interpreted as text, but you want them as dates. I have a powershell prototype sample here which ...


2

I would do the following: priorize the incremental crawl with "high" priorize the new content source with "low" limit the requests to the new site in crawler impact rules start the crawl on friday night and pause it on monday - repeat until you have the main chunk indexed (use powershell to automate) With this the impact should not be that hard.


2

If you want to append to the url, you can add something like this - osssearchresults.aspx#Default={"k":"Amit","o":[{"d":1,"p":"Created"}]} Above, k = queryText ; d - can be 0 or 1 for specifying the sorting order ; p - parameter based on which you want to sort. Further you may look into this link Also if you are using result source for search results, ...


2

This is not possible as FAST supports FQL (FAST Query Language) and not regular expressions. Your best bet is to create an external processors which uses regexp to find social security numbers. If you find a match, assign the value "true" or similar to a crawled property. Then create a managed property of type bool which you map this crawled property. When ...


2

How are you adding the Core Search Results onto the page? I wonder if you populated the "Selected Columns" property, if it is being left blank or has invalid data.


2

what you need to do is the following: make sure that your content is indexed lookup the crawled properties, and find your custom column in it. It starts with ows_ and it ends with the internal name of your custom column. create a managed property that is mapped to your crawled property re-index go to your search center, add your managed property to the ...


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 ...


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

It seems that you have to add LastModifiedTimeStampField property to your Finder method. Take a look at this blog posts series from Todd Baginski, especially at this one - The LastModifiedTimeStampField property on the finder method instance is set for two reasons. So search results will display the last time the data was updated So the ...


2

The usage data comes from a SQL Database named WSS_UsageApplication. When you provisioned web analytics, a reporting database was created. You can query this database safely from my understanding because it was designed for reporting. It is an aggregation of data from WSS_UsageApplication. Some query data is in a table named WAQueryTextAggregationByDate. My ...


2

Figured it out with the help of the following link: http://www.sharepointsteve.com/2010/10/making-custom-user-profile-properties-searchable-in-sharepoint-2010/ Lot more to this than I expected ... but it does work.


2

FAST Search for SharePoint includes an advanced filter pack which will convert over 200 formats, which is not ifilter based. But I don't think it will do exif meta data. Office formats on the other hand has meta data extracted. As for doing exif you can install an ifilter for this, as FS4SP will use ifilters in addition to the advanced filter pack.



Only top voted, non community-wiki answers of a minimum length are eligible