6

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


5

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.


4

You can add "Path:http://urlofyourlist" to you KQL query.


4

To achieve the goal, you can go to configure search navigation. Here are the steps for your reference: Go to the Site settings page, click Search Settings under Search. In the section of Configure Search Navigation, click Add Link to add the the following links: 1). Title = Everything; URL = /search/pages/results.aspx 2). Title = People; URL = /search/...


3

I found the solution instead of using the SearchServiceApplication which causes the issues with permissions, I use this piece of code: RemoteScopes remoteScopes = new RemoteScopes(SPServiceContext.GetContext(site)); And it works like a charm.


3

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


3

Goto the search page where you are showing the results Edit the Search results webpart Edit the Query change query to speaker:{searchboxquery}


3

How do I enable same behaviour in SP 2013? Unfortunately , you can't do the same behavior in SharePoint 2013 at the default search box that is shown on top right corner, This due to SharePoint 2013 introduces the Enhanced List toolbar feature, so the Search behavior has been divided into two section [Search this site] this the search box that is shown on ...


3

Those are called refiners. You can customize these by editing the page. Click the gear icon and select Edit page. Tick the down arrow on the refinement web part and select Edit Web Part. In the web part properties, click the Choose Refiners button and add in any refiners you want. OK out as necessary and save the page. If your fields aren't showing up, ...


3

This is absolutely possible. Please check the search service and then the crawl log. You can identify the specific document URL and then select remove this from index option. Central Administration --> Search service Administration Click on Crawl Logs --> Select the content source --> Click the Success Count Link Select the specific URL from the search ...


2

The People scope by default sets the results page to peopleresults.aspx. On the PeopleSearchBoxEx control add UseSiteDefaults="False" <SPSWC:PeopleSearchBoxEx ID="MySiteGlobalSearchBox" FrameType="none" HonorUseSiteDefaults="true" IsMysiteSearchBox = "true" SearchResultPageURL="/Pages/colleagueSearch.aspx" UseSiteDefaults="...


2

I suggest you recreate the "Animals Metadata" column WITHOUT any special characters, and then RENAME it afterwards. This is SharePoint best practice due to how internal representations of names are stored. A space becomes x0020 when encoded and may be further encoded to _x005F_x0020_x005F_ and so forth. You can see how this will develop into a nightmare ...


2

You can add a Rule to your scope to exclude all aspx files. Using the answer I posted here: https://sharepoint.stackexchange.com/a/51338/2881 Scope Rule Type: Property Query Property Query: FileExtension = aspx Behavior: Require In order to have the FileExtension property be available you will need to go to Search Administration within Central ...


2

You need to include all content as a rule by default, your exclusion then works with this to make the list.


2

Ok, I found the solution: This line from xml should have been deleted: <Property Name="ScopeDisplayGroupName"></Property> When i delete that line and redeploy, I receive the expected results. Hope this will help other people.


2

This kind of functionality is actually available out-of-the-box as Membership sites, where users on their MySite can see what sites they are a member of. SharePoint maintains a list of membership sites for each user - that is a list of all sites where the user is granted access through the SharePoint Member group on sites. See My Sites overview on MSDN and ...


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

I have come across this too, and yes, viewscopes.aspx causes the standard display groups to be created. I have written a post about my findings, and the work around I used: http://danielflint.im/2014/01/working-around-getdisplaygroup-throwing-invalid-cast-via-powershell/ Here's the work around: Add-PSSnapIn Microsoft.SharePoint.Powershell -ErrorAction:...


2

Change the default filter for the Search Results Web part to exclude Web pages. There are a number of ways to do this. You can try things like adding "AND NOT FileExtension:ASPX" to the query.


2

Just deactivate Document ID Service and reactivate it. Source: Click Here Or try this Open central admin Go to Operations Go to Services on server and located your index server On “Office SharePoint Server Search” click “Stop”. This deconfigures it. Now click “start” Then click “Shared Services Administration”, hover over the failing SSP and select edit. ...


2

You can only refine on Managed Properties that are marked as Refinable. There is an out of the box Managed Property "ContentSource". You can try changing the Refinable attribute to Yes. You then have to run a full crawl of your content sources to populate the property. Once the crawl is complete you SHOULD be able to go into the Refiner web part and add the ...


2

When you are testing Searching SharePoint it is vital that you look at the URL that is returning your search results. There is this "intermediate" search page "OSSSearch.aspx" that returns "Site Collection Scoped Results" (the scope that is selected when you choose to "Search this site"). When you are on that page you are seeing results from the site ...


2

Yes you can. Go to Site settings > Site collection Administration > Search Settings on the site where you want to be able to search for everything. ( You have to do the following steps for every sitecollection. ) Set "Search Center URL" to your global search center url. ( url/sites/searchcenter/pages) Uncheck "Use the same results page settings as my ...


2

Use the 'selectproperties' query string parameter


2

You will need to convert EdwSearchTag into a managed property. After that you can run searches by adding EdwSearchTag as a search term in your query (for e.g. EdwSearchTag contains denials, will return only search results for column values containing denials) Here are the steps: -Choose a field in a list or document library. -Make sure some items in the ...


2

Should have waited 10 min with that post.. $ssa = Get-SPEnterpriseSearchServiceApplication -Identity "Search Service Application" $scope = Get-SPEnterpriseSearchQueryScope -Identity SomeScope -SearchApplication $ssa $scope.Rules $rule = Get-SPEnterpriseSearchQueryScopeRule -Scope $scope -Url http://sp2013 -Identity 3 $rule.MatchingString = "http://sp2013/...


2

Try with the content types. Limit the search results for respective content types. Let me know if you have any questions


2

How many site collections are we talking about? Why do you have two search service applications? If you want to have a split on search service application's usage, then its better to have it at web application level from a logical architecture perspective. Central admin -> Application Management -> Service Application Association page to identify service ...


2

You can update the search results webpart to exclude the word 'How do I' by Go to the search results page Edit the page Edit the search result webparts Click change query Add (and -How do I) to exclude the keyword from the search see image below Ref: https://www.mavention.nl/blog/exclude-external-users-search-results-office-365 https://social.technet....


2

SharePoint only supports "suffix" wildcards. You can only do mysite.org/projects/2016/proj* OR mysite.org/projects/2017/proj*. Another approach would be to query on the WebTemplate type if you are using a specific template.


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