If you have specific queries that you want indexed, I suppose you could create a list of links like so:
http://yoursite/PropertySearch.aspx?status=past http://yoursite/PropertySearch.aspx?status=current Or http://yoursite/PropertySearch.aspx?propertyName=status&propertyValue=past http://yoursite/PropertySearch.aspx?propertyName=status&propertyValue=current It depends on how you pass the query parameters into the page, however my solution only focuses around putting property names and values onto a web page, so that a search engine may crawl the content. It's really up to you to determine how you would want to implement it, but it's a simple solution. When you write custom code, you really get to do whatever you like, so if you want something more advanced, just design and implement it. You didn't mention anything about wanting structured queries in the original post, and I'm not aware of all of your requirements. Cheers, Matt -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Williamson Sent: Sunday, 9 December 2007 10:01 AM To: [email protected] Subject: Re: [OzMOSS] Does/Can the Search Engine index the SPWeb PropertyBag? How would that allow for discrete property querying for the search engine using the SQL syntax object model though? It is our number one requirement. Easy example: If you had a site property with "status" which can have either "current" or "past." How would I write a custom search engine query that returns all sites with "current" status? That one seems to work very well for plain fulltext queries and for search engines that cannot handle structured data, but we're trying to levarge the structured query power of MOSS for this. On 12/7/07, Matt Lynch <[EMAIL PROTECTED]> wrote: > "Complicated" is a relative term and there is a thunderstorm about to roll > in, so I guess there is more time to spend on the task. :) > > The custom aspx solution includes the following tasks: > > 1 - Create a ASPX page. If you want to make it pretty, define a Web content > form that refers to one of Sharepoint's master pages. > 2 - Add a ObjectContainerDataSource[1] and a Repeater to the page. You > could use a grid or something else if you prefer. Don't use a .net 3.5 > ListView, because they are not SEO friendly. > 3 - Edit the item template for the repeater, and add a label and hyperlink > to the item template. > 4 - Bind the Text property of the label to the property name. > 5 - Bind the Text property of the hyperlink to the value name. Also bind > the NavigateUrl property to the name of your site, optionally passing the > value of the property as a query string. > 6 - Handle the Load event for the page. In the event handler, obtain a > reference to the property bag and assign the reference to the DataSource > property for your ObjectContainerDataSource. > > If all is well, the page should be under 100 lines of markup and code. The > page can then be crawled by *any* search engine, be it Sharepoint, Search > Server, Google, etc. > > There is probably a dozen other ways to get this done, but I don't find this > method complicated at all. It's code - but be not afraid - writing source > code is fun. > > Matt Cossier's example might be better if you already have defined managed > properties, because it's a no code solution. The option I have outlined > above should work for basically any bit of data you wish to access, > regardless of if it's a managed property or not. > > Cheers, > > > Matt > > [1] The ObjectContainerDataSource is a ObjectDataSource derived class that > makes it quite easy to bind to a list of objects, such as the items from a > property bag. It's a Open Source component that the Patterns and Practices > team have released. > > - If beauty is in the eye of the beholder, blind people must think that > everyone is gorgeous. > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Mick Badran > Sent: Friday, 7 December 2007 1:26 PM > To: [email protected] > Subject: RE: [OzMOSS] Does/Can the Search Engine index the SPWeb > PropertyBag? > > Guys - it's all sounding pretty complicated.....especially for a Friday. > > This comes from the days of Site Server....way back when. > > Bill - the webpart is a solution, but does the free text thing, grand scheme > it is pretty crap with large indexes. Your site almost never comes up and is > not recognised at a 'site'. > > My solution: > - pick a page or create an accessible page within your site (as opposed to a > page that is hidden and has no links to it) > - using the HTTP protocol handler (this guy is pretty cool - there's an > article somewhere on MSDN about this) > this guy looks in the HTML HEAD tags for its 'metadata' > - the general format is <META NAME='propName' CONTENT='propValue' >. > This means that you can populate these with anything - that's all you need > to do from your chosen page. > > In fact you can even set the file location property to something else other > than the assumed default 'http://server/sites/yoursite/default.aspx'. I've > had to use this with various imaging systems that have a 'viewer' page and > all requests when viewing items should go through this page. > > - indexer does the rest (make sure you do a full build after all this is in > place) > > Problem solved - let's get out and enjoy the sunshine. > > HTH, > > Mick. > > ________________________________________ > From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Matt > Lynch [EMAIL PROTECTED] > Sent: Friday, 7 December 2007 1:00 PM > To: [email protected] > Subject: RE: [OzMOSS] Does/Can the Search Engine index the SPWeb > PropertyBag? > > What's wrong with passing parameters to the page, and then filtering with > your own code? Custom IFilters are a <%= expletive %> to debug. > > If you wanted to be really nice, you could then write a really small Web > Part that allows users to specify the parameters. Clicking search would > open the custom ASPX, passing the parameters via the URL. The custom ASPX > page could then obtain the parameters from the request, filter the > PropertyBag as required and then display the output. > > You could do it completely with web parts too, the implementation would be > almost the same. > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Ishai Sagi > Sent: Friday, 7 December 2007 12:44 PM > To: [email protected] > Subject: RE: [OzMOSS] Does/Can the Search Engine index the SPWeb > PropertyBag? > > Sounds like it will be easier to create a custom iFilter? > > ________________________________________ > From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Bill > Williamson [EMAIL PROTECTED] > Sent: Friday, 7 December 2007 12:36 PM > To: [email protected] > Subject: Re: [OzMOSS] Does/Can the Search Engine index the SPWeb > PropertyBag? > > I suppose I could (cringe) write a BDC adapter which returns the > SPPropertyBag properties for a site.... > > On 12/7/07, Ishai Sagi <[EMAIL PROTECTED]> wrote: > > One way that I saw people do it is write a custom web part that displays > the properties on the site's home page. the home page gets indexed into the > full text index - so you can search for the terms in them. > > > > For doing a "property search", I only heard of the single item list > option. > > > > > > ________________________________________ > > From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Bill > Williamson [EMAIL PROTECTED] > > Sent: Friday, 7 December 2007 11:38 AM > > To: [email protected] > > Subject: [OzMOSS] Does/Can the Search Engine index the SPWeb PropertyBag? > > > > If I add properties to the SPWeb property bag, is there ANY way to get > > the search engine to index those properties? > > > > I'm trying to get around the hack-ish solution of "Create a > > single-item list" for doing site-relevant properties, and the property > > bag is a great way to do it (in fact it's how they do the BDC > > integration, so I know it's the "right" way to do it), but if you > > can't search it then it's pointless. > > > > > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > > Powered by mailenable.com - List managed by www.readify.net > > > > > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > > Powered by mailenable.com - List managed by www.readify.net > > > > > > > > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > > > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > > > > ------------------------------------------------------------------- > OzMOSS.com - to unsubscribe from this list, send a message back to the list > with 'unsubscribe' as the subject. > Powered by mailenable.com - List managed by www.readify.net > > > ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com - List managed by www.readify.net
