Creating scope using Property Query

Question

I'm trying to setup a search scope that uses a Property Query, but not getting the results I expect. The idea is that a specific site within my site collection has a set of pages that use taxonomy terms, and I want to create a search scope that only returns results where the page uses one of those terms.

e.g. let's say I have the following site structure

myserver.com/
myserver.com/support
myserver.com/support/v1
myserver.com/support/v2
myserver.com/marketing

I've 'tagged' all the pages in /support/v2 to use a Term Set called "Product", which has terms of "Product OnSite", "Product OnDemand" and "Product2".

I'd like to create a scope that only returns results where pages in "/support/v2" have a "Product" value that includes "Product OnDemand".

My understanding of how this should work is as follows:

• Setup a Term Set, with Terms
• Create a new column in the pages library for a specific site (in the example, /support/v2)
• 'tag' each page within the site (/support/v2) to use one or more of the terms
  within Central Admin,
• do a full crawl of the sitecollection
• Create a Manager Property that maps to the crawled property Product (or ows_Product?)
• Create a scope that has a rule where Type is "Property Query", Property Query is "Product" = "Product OnDemand", and behavior is "Require"

When I do the above, I get 0 items in my scope within Central Admin, and also when viewing scopes at the sitecollection level (I often see more items at the sitecollection level than in CA, even if CA shows 0 items)

I'm using SharePoint 2010 Server Search, as opposed to Fast or Enterprise (i.e. ootb SharePoint 2010 Server)

Is my understanding of how this works flawed?
Are there other steps I should be taking?
Any tips on what else I can look at the make this work as expected?

Cheers
Kevin

---

A true software developer is one who, when told to 'Go to Hell', sees the 'go to', rather than the destination, as harmful.

Answer 1

Hi,

Did you do full crawl after creating the managed property and Scope? you need full crawl whenever you create a new property that's how search picks it up...

Cheers

Singh

---

B Singh

Answer 2

I did, yes. Looks like one of my bullet points in the original question didn't show properly, but I did do this.

---

A true software developer is one who, when told to 'Go to Hell', sees the 'go to', rather than the destination, as harmful.

Answer 3

try to change the property query from Require to Include....

---

B Singh

Answer 4

tried that too

Is my understanding of how this works flawed?

---

A true software developer is one who, when told to 'Go to Hell', sees the 'go to', rather than the destination, as harmful.

Answer 5

While creating Managed Property, did you check the box saying "Allow this property to use in Scopes"???

---

B Singh

Answer 6

Hi - Yup. I just checked that, and it's definitely checked to Allow this property to be used in scopes.

Thanks for asking these questions :)

---

A true software developer is one who, when told to 'Go to Hell', sees the 'go to', rather than the destination, as harmful.

Answer 7

try one more thing. Instead of checking scope, if you go to search center site and search for Product = "Product OnDemand" OR try  Product= Product OnDemand (without quotes). This should first display results.. then only we can expect something in scopes. if search results are not coming, then there is something different issue. try on enterprise search center site first

---

B Singh

Answer 8

Sorry for the delayed reply - I ended up not working yesterday due to illness.

I just tried doing a search for 'Product="Product OnDemand"' (with double quotes, not single) and this seems to show the expected results. I'll need to check that with the content author who added the metadata to the pages, but this looks right!

Essentially I have 2 scopes in play here:

1) All Support (which has a rule hostname=myserver.com/support)

2) V2 Support (which is the one where I'm trying to get only "Product OnDemand". The pages I expect are within the myserver.com/support/v2 folder.

My testing of 'Product="Product OnDemand"' was done in the first scope, and only result with a location within the /v2 folder where shown, which is what I would expect.

Assuming that this search does indeed show the correct results, what implications are there for my scope? Should I be entered the property query value with quotes too? To me this suggests that Managed Property is correct, so it must be the scope itself?

Thanks for the help so far

Kevin

---

A true software developer is one who, when told to 'Go to Hell', sees the 'go to', rather than the destination, as harmful.