You are not logged in Log in Join
You are here: Home » Members » TheJester » Zope Quick and Dirty Search Engine and Indexer » dc_view
Log in
Name

Password

 
Link icon Forgot your password?
 
Print


Dublin Core Elements

The Dublin Core metadata element set is a standard for cross-domain information resource description.
Element Description Value
Identifier resource ID http://old.zope.org/Members/TheJester/ZQuadSex
Title resource name Zope Quick and Dirty Search Engine and Indexer
Description resource summary ZQUADSEX: Zope QUick And Dirty Search Engine and indeXer What's it for? Well it's for making a search engine, based on content you provide, either by o Submitting URLs to be indexed (which are not stored), o Uploading files to be indexed (which are not stored), o By using the <dtml-indexer></dtml-indexer> block tag to submit content for indexing. Using it: Install a 'Text Indexer' product in your tree somewhere. Then you can submit URLs, or Files to be indexed into it (via dtml if you want). You can also use <dtml-indexer></dtml-indexer> to wrap content to be indexed. URL/Tag based indexing uses the absolute_url() to determine an ID for it, so if you use variables to alter the display of your page, then you'll need to do some work to get it to work. *** Warning: the stats page has some code commented out, uncomment it for an interesting view of your index, but, it'll take a *long* time to render. ------------------------------------------------------------------------ You can specify the default search mode: o And Mode: all words in a query must match o Or Mode: any words in a query can match You can override the search method dynamically if you want to. You can specify an amount of text to keep as a summary. You can specify a threshold (as a percentage of the total) for words to ignore in searching. Ignored words do not abort an 'and' search. You can specify a minimum period of time before reindexing occurs (useful for <dtml-indexer>. o Indexing does not occur if content has not changed since last indexing. o URL indexing removes html tags before indexing so 'font' and 'td' don't end up being the most frequent words in your index. Indexing is quite slow, but searching is quite quick, queries on 40Mb of data (that is data submitted to be indexed), takes on average less than .5 second. Can I do 'advanced' searches? Short Answer: No. Long Answer: Yes. Can it be made faster? Yes, it's not particularly optimised right now, there's quite a few things that can be done to make things run quicker, smoother, nicer, pick your superlative. Will you eventually do that? Probably not, unless someone wants to hire me to work on it, its sufficient for my needs right at the moment (although I do have a version thats tweaked for my dataset).
Creator resource creator TheJester
Date default date 2001-11-23 03:40:04
Format resource format text/html
Type resource type Software Package
Subject resource keywords Content Object, Helpers, Navigational, Server
Contributors resource collaborators
Language resource language
Publisher resource publisher No publisher
Rights resource copyright


Additional Zope Elements
Element Description Value
CreationDate date resource created 2001-11-23 03:40:04
ModificationDate date resource last modified 2001-11-23 03:40:04
EffectiveDate date resource becomes effective None
ExpirationDate date resource expires None

Backlinks: via Google / Technorati

Copyright (c) 2011 Zope Foundation. All rights reserved. Legal | Contact
If you can read this text, it means you are not experiencing the Plone design at its best. Plone makes heavy use of CSS, which means it is accessible to any internet browser, but the design needs a standards-compliant browser to look like we intended it. Just so you know ;)