Can we create scope in Site collection?

 Hi All,

I know that we can create scopes from SSP. However, what if I don't have access to SSP and I want to create a new scope for my site collection? Is it possible to do the same?

I am a site collection admin and I am trying to create a scope for my site collection. I restrict my scope to just one list still I see 0 items in the scope. Is it because scope can only be created at SSP?

e.g. I have a list "my list". I want my scope to search withing that list only

so I have a rule for "My list scope" as "http://test01/site/My Site/lists/My list" to include everything from that. That list has 100 items but the scope says 0 items.

Please help.

 You create your search scopes from within the SharePoint UI.  Click Site Actions, Site Settings, Modify All Site Settings.

In the Site Collection Administration column, select Search Scopes.  Click the new scope button and create your new scope.

On the View Scopes page, click on the scope you just created and click Add rules and set the rules for your scope.  After you are done with your scope rules click OK. 

On the View Scopes page you will see a status that indicates how long it will be before the scope will be available.  The only way you can force the scope compilation job to run without waiting is to go into your Shared Services Provider within Central Admin and manually start the update.

- Ben

 Hi Ben,

I have done the same already but somehow the scope is not filling up and showing 0 items even after the update. Here are my rules for the new scope:

What could be the issue? Please help.

Thanks,

Shell

The Require rule is most likely causing your problems.

 Hi Bob,

I have tried all the permutations and combinations now. Removed the "Required" rule, only had include rule but still it shows me 0 items after whatever rule I write.

Can someone please send me a set of rules which I can try to see if the scope fills items or not?

The other thing to note is the scope will be built after the next crawl.  What is your crawl schedule?

A simple scope to try would be to set the contentclass, as an inclusion with a value of STS_ListItem_DocumentLibrary.  This will include all document items.

 Hi Bob,

The scope update schedule is every 15 minutes. Also, I tried the all documents scope you suggested and it worked like charm! so, why I am not able to create a scope only limited to a list.

I have a list at: http://test01/sites/sandbox/Lists/MyList

I have a scope created as:

Include -> http://test01/sites/sandbox/Lists/MyList -> 300 items

But it still shows me 0 items after scope gets updated. Please suggest.

The only reason I can think of; the content of that list is not being crawled.  Remember, a scope pulls from crawled data.  Make sure the list is being included in a crawl.

 Sorry about not replying earlier, I was not receiving any notices concerning this post via email.

Here's an article on MSDN about setting a scope for a list...

http://msdn.microsoft.com/en-us/library/cc299453.aspx

They go on to showcase federated search in this article, but I would double-check the steps concerning the list scope and crawling content to see if that helps you.

-Ben

 Forgive me if you've already done so, but have you reviewed the permissions on the folder you want to index?

 Since Friday I have been stuck into some other issue. I have modified the scope with new rules but the search update is not happening and I am stuck with message: "New scope - Ready after next update (starts in 1 second)" since Friday.

I don't have access to central admin site and upon inquiring the relevant group I found that the search updates are running regularly as before but this scope is stuck......

Can someone throw some light on this?

I would have to look at your configuration to further understand what is going on.

I had the same issue - turned out to require an incremetal crawl to be kicked off per Ben's link (http://msdn.microsoft.com/en-us/library/cc299453.aspx). When I checked the scope created over the list, the items were there (count > 0).

Cheers

John