Tag Info

Hot answers tagged

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

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.


1

By utilizing a content enrichment webservice you could pass in the HTML and use eg. HTML Agility Pack to parse it. The write out the values you want to a new managed property. So no crawled properties involved. I'm also a bit curious as to the use case here.


1

The odd time shows up because FAST tries to automatically create 'bins' to put your search results in when you don't tell it exactly how... You said you have many records that have an uploaded date of 21 and 22 August -- FAST figured out the way that it felt like partitioning your results would be to put them into two separate bins with a dividing line ...


1

I think in your refinement panel Xsl, uploaddatedt property is defined as Range Property and not Simple Category. Regarding your first question you already said you have items with that date, So you will get that data only the format that you are getting is weired and to change that you need JavaScript to xsl functions And your next query could be solved ...


1

First of you should use SPContentType and not ContentType. For some reason ContentType seems a bit unstable but the "special" SPContentType always works. In addition to the suggestions by @Sane.Amit you can edit the search result web part and change the sort order drop down values, then uncheck it again as explained in my post: ...


1

This isn't really possible without having multiple farms each with a separate Search Service Instance. I would suggest you basically split out your 1.5TB of content into a separate farm with a dedicated Search instance. You can even use HOSTS entries on the crawl servers so they have their own local dedicated WFE servers for the crawl process to iterate ...


1

Like most pages in SharePoint, the search page is made up of web parts and zones. You can move web parts around into different zones or create a new page layout with zones where you want them. You can also use CSS to customise further as needed. So yes, you can achieve a very different interface without losing functionality.


1

It could be the fact that you haven't indexed content into the managed property yet. Also make sure the property is queryable.


1

Search is not covered in JSOM for SP2010 - try using spservices: http://www.itidea.nl/index.php/example-of-using-the-spservices-search-web-service/


1

Use the following to restrict to only these properties a:"myPropertySearchA" OR b:"myPropertySearchB" OR C:"myPropertySearchD" Reference: Using Operators in Keyword Queries and Property Restriction Keyword Queries



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