Tag Info

New answers tagged

0

You can target managed properties in your query by adding them to the query term: customSearch:yourTerm


0

As Jesus told..The best way to skip the crawling is to create crawl rules for the diffirent sites. Following is the PowerShell Command using which you can incorporate crawl rules. $Path = "http://SharePointSite/sites/test/*" $SearchApp = Get-SPEnterpriseSearchServiceApplication if ((Get-SPEnterpriseSearchCrawlRule -SearchApplication $SearchApp -Identity ...


2

What about just setting up the Enterprise Search Centre and changing the 'Which search results page should queries be sent to?' property on your sites? You can also set this at the root and have your subsites inherit this property. This is what the Search Centre was made for: Searching across all content.


0

I finally found the solution to the problem. Thanks to Mike Lutge for pointing me in the right direction. The funny thing is that although spSite.UserToken and spSite.RootWeb.CurrentUser both reference the user performing the search query, the search still seems to be run using the System Account context. I believe that the either the KeywordQuery or ...


1

You have a few options. Under site settings you should have a Search and Offline Availability option where you can set it to not show in search. You can add a query rule that removes results based on site URL's. If they are unique URL's you will either need seperate rules for all of them or make sure the Query is configured to retrieve the correct ...


0

Here is the solution: Go to Search Center Site > Site Settings > click Search Schema under Site Collection Administration Type refinablestring in the Managed property text box Click on the RefinableString02( you can select any other refinablestring) and Edit it Add ows_SiteName in the Mappings to crawled properties and Give a unique Alias name. I have put ...


0

If the code you have posted above is running in a SharePoint 2013 app then in order for your search query to be executed as the user you will need to add the following to your AppManifest.xml: <AppPermissionRequests> <AppPermissionRequest Scope="http://sharepoint/search" Right="QueryAsUserIgnoreAppPrincipal" /> </AppPermissionRequests> ...


2

SiteTitle is a Managed Property in search but it is not set to be "refinable" by default. Go to Central Admin > Service Applications > Search Service and then Search Schema. Search for "SiteTitle" in the managed properties. You'll see that the property is set to "Queryable" and "Retrievable" but not refinable. Edit the Managed Property and set it to be ...


1

I will admit I haven't tried this yet, but I was looking at the instructions for adding refiners here: http://blogs.technet.com/b/tothesharepoint/archive/2013/11/11/how-to-add-refiners-to-your-search-results-page-for-sharepoint-2013.aspx Took a look at the available mappings (as part of my own question I'm trying to answer) and noticed in the SharePoint ...


0

I would have two search results pages: one for English, one for French, maybe each with a nation flag at the top for both pages that links to the culture's search page (preserving the search). You can even have some javascript on the search results page that hits the user profile service (through REST) that will try to determine which search result page to ...


0

Take a look at the SectionNames mananaged property, unfortunately it's not searchable. This leaves you to create a content enrichment web service and extract the titles yourself and put them in a custom managed property.


3

See http://blogs.msdn.com/b/sharepoint_strategery/archive/2013/12/09/sp2010-search-query-load-balancing-explained-part-2.aspx (see the special note on SharePoint 2013) As per the article in SP2013 you can stop SQ&SS on 3 servers, and just leave it running on the server running on Query Processing Component. you can stop it using Manage services on ...


0

We had a similar issue with FAST and we opened a support case as well. We were indexing 7 TB worth of data totaling around 3 million items. They said that disk IO was our major issue causing the timing out so we had to order new FAST servers. We ended up going with: 96 GB of RAM 2 x 6 Core Xeon CPUs 8 x 300 GB HD - 2 mirrored for OS, and other 6 in a ...


0

Assuming you use SP2013 The search you do on "people" is basically a standard search with an extra filter parameter that indicates only to return people results. Create a custom content type and make the search return: people results or items with your custom contenttype. The difficulty will be mapping the properties correctly (reuse existig columns!). ...


0

Read this> http://blogs.technet.com/b/tothesharepoint/archive/2013/03/06/from-site-column-to-managed-property-what-s-up-with-that.aspx And this> http://technet.microsoft.com/en-us/library/jj613136%28v=office.15%29.aspx Important note: Only site columns that contain values automatically become managed properties when they're crawled. Regular columns do ...


0

Central Admin -> Application Management -> Service Applications -> Search Service Application -> Metadata Properties (On the left side under Queries and Results) Find the “Title” field in the list of properties and open it. Under “Mappings to crawled properties” -> Add Mapping for “Custom Column you want to display” and save it. Run a Full Crawl. Now ...


2

Take a look at MS's tech diagrams for SP2013, http://technet.microsoft.com/en-us/library/cc263199(v=office.15).aspx, there's a lot of useful layouts and architecture examples here. To answer your question, no, I generally don't put Query on all boxes, just a couple of dedicated ones, or in your case, on both app servers. It depends on the hardware specs of ...


0

The standard query for everything is (w/o people results) is: {?{searchTerms} -ContentClass=urn:content-class:SPSPeople} So if you want a "this site only" scope you should add the url as filter either with path:"http://hostname.fqdn/sites/site1" or with a Query Variable path:"{site.url}" You can see the substitutions in the query builder wizard in ...


1

I think your Search Settings are invalid - in particular the redirect to the Search Center. Verify that you have /Pages appended in the Search Center Url. Verify that the Pages it redirects you to, exists (e.g. results.aspx) - they are in the Pages library. Example: http://i.imgur.com/kcxc2uk.png


1

The reason it fails is due to a code bug in Microsoft.Office.Server.Search.Administration.GetErrorMessages. In the loop it checks if allKnownErrors has the key, and of course it does as it's looping that dictionary. The code should check if dictionary2.ContainsKey instead. public Dictionary<int, string> GetErrorMessages() { ...


0

I've found a solution/workaround to get the refiner working: The only thing I have to do is to change the settings of the "FileType" managed property to respect priority and move my own crawled property to the first position. With this configuration the file type of the crawled property "Return.Extension" is used and not value of the "FileType" crawled ...


0

Look in the Search Service Application and find the Metadata Properties. The bindings of the properties are all set there so you can add your custom field into the "Title" property.


0

If you have created the scope correctly and then changed the Search Results Web part to use that scope it should only return results from the scope. I would recheck the scope and the settings on the results web part.


1

It depends what exactly you want, but yes that is entirely possible. You want to add to your search query the term: path:http(s)://domain/path/to/site/collection That will restrict your results to only include results who's url contains the path specified, or in other words, who are part of the specified site (or site collection) or it's sub-sites. To ...


0

That is O365, limitation and limitation. Did you try Search Results Web Part. You need to configure it and it will return the results on the base of query. I know its not solution but still little alternate. http://office.microsoft.com/en-us/support/sharepoint-help/sharepointsearch/about-configuring-the-search-results-web-part-HA102848383.aspx


0

You could use decodeURI() (http://www.w3schools.com/jsref/jsref_decodeURI.asp) function getUrlVars() { var url = window.location.href, vars = {}; url.replace(/[?&]+([^=&]+)=([^&]*)/gi, function(m, key, value) { key = decodeURIComponent(key); value = decodeURIComponent(value); vars[key] = value; }); ...


1

Yes, I believe this is possible. The Result Type for the feed posts is SharePoint MicroBlog Post. If you have an Enterprise Search Centre provisioned, these results will usually show under the 'Conversations' tab after 'Discussions'


1

Instead of looking directly for the folders, you'd probably want to query the 'Path' variable for all items where it contains 'leader'? Path:{Site.URL}/leader Plus, if you configure this at the root site collection, this should get all other site collections below as well. {Site.URL} could also be exchanged for {SiteCollection.URL}


0

I don't know witch SharePoint are you using 2010 or 2013 here is a good answer how you can query folders with CAML query. <FieldRef Name="FileDirRef"></FieldRef> <Value Type="Text">Server Relative URL of the Folder</Value> You can get the folder using SPQuery.Folder and search for SPListItems from code behind.


1

You'll need to make sure that your custom column is a Managed Property in your Search Schema. By default, all site columns are also created as Managed Properties, but if you created the custom column in the document library itself, it won't be in the Search Schema as a Managed Property, it will just be a Crawled Property. In Central Admin, go to your ...


0

The only option I found was to do a search as so: NOT (MetadataProperty:"ABC" OR MetadataProperty:"DEF" OR MetadataProperty:"GHI") and send it Search Query JSON using window.location.href or entering it in the search box http://MyServer/site/Searchpage.aspx?Default={"k":"NOT (MetadataProperty:\"ABC\" OR MetadataProperty:\"DEF\" OR ...


0

The most difficult part of your requirement is the "non-document" item. Can you explain that scenario? A document item must have a document. If you want to change that behavior you may try to add a non document content type to a library, but I would think that should fail. Next you could try to "fake it" with a folder or Link to Document content type. ...


0

You can enhance the end-user search experience by mapping crawled properties to managed properties. Crawled properties are metadata (such as author, title, or subject) that are extracted from documents during crawls. Managed properties can appear in refined searches and help users perform more successful queries. Refined searches can be ...


1

The search in the osssearchresults.aspx happens by passing the parameters via URL. If you check the search URL of a site2 after clicking on the Search button, the url is like as follows: http://<Server>/sites/site2/_layouts/15/osssearchresults.aspx?u=</sites/site2>&k=<Searchword> Now u=</sites/site2> is getting changed in every ...


1

Rather than send your uses to the useless OSSSearch Page, why not just configure the Site Collection to send them to your search center. This way you will get results from all sites? Alternatively you can teach them what to expect when searching a list (just list content) a site (just site content) and "everything" all site collections.


0

I can't think of a way to do this without custom code in 2010. You might be able to do it in 2013 with a combination of Query Rules and Display Templates, but in 2010 you don't have the User property features out of the box.


0

In the search settings for the site collection you need to choose "Enable custom scopes (such as "All Sites") by connecting this site collection with the following Search". Seems you selected "Do not use custom scopes. Use only contextual scopes (such as "This Site"). Display results in the Site" and hence the contextual results.


1

A retention policy may do the trick: Library Settings => Information Management Policy settings => Choose Content Type => Enable Retention => Add a Retention stage => Set up your rules http://www.future-processing.pl/blog/retention-policy-in-sharepoint-2013/


0

Try the HitHighlightedProperties and the HitHighlightedSummary properties. These should contain the summary information for each hit. You will need to format these values and convert them to HTML (using XSLT, for example). ...


1

Yes Sure :) You Could create a Content Source of FILE SHARE type. And give \intern.contoso.com\data as Network Path. Full Crawl the Content Source and your results will be ready. Please check the snapshot for FileShare Content Source option.


4

Yes, you can. Crawling file shares is very easy to set up, and permissions are accounted for - so there is no risk that users find information they don't have access to. In Central Admin Search Service Application, add a new Content Source. Specify your file server and set up a schedule. Do a full crawl and you're up and running in no time.


1

I think you look at the problem from the wrong view. You actually do want to include allitems.aspx to be crawled but none of the other views. To make this work you need to make a crawl rule that includes allitems.aspx as order 1, and an exclusion rule that skips all other views - like this: With this all af your documents are beeing crawled only once, ...


1

New custom server columns won't show up as crawled properties until you've populated that column with data and a search has crawled it. So for instance, you create a new list and use your new server columns in that list. You must create a new item in the list and you must populate each new server column field with data (no nulls) and then run a crawl.


0

When creating regular expressions for crawl rules you need to include the protocol (http(s)://) So it must start with http:// (https://) then follow by your pattern. Else SharePoint will be kind and add it. I think you are looking for something like this http:///forms/allitems.aspx[?] In case there is a link pointing to allitems.aspx with parameters.


0

In order to search on the title is to implement a keyword query with the Title managed property. For example, to search the title for marketing documents, I would enter something like this.Title:"Marketing"


1

You can't in 2007. Prefix matching was introduced in 2010. You can try using Search SQL syntax in 2007, but that is deprecated in 2010 and removed in 2013.


0

The search results process in 2010 is pretty complicated, it get's easier in 2013. You have to work with XSL, so you should not need to write code. Here is an article I wrote on the process for 2010: http://www.ableblue.com/blog/archive/2011/09/30/take-control-of-search-xsl/


0

To be able to search for files with the tif/tiff extension, you need to make sure that you enable the "Windows TIFF filter" from the server manager features. This blogpost explains the steps to take. Make sure to follow the steps and you should be good to go. Search TIFF files in SharePoint 2010 Some additional information from Microsoft about the ...



Top 50 recent answers are included