Hi,
last week i got webinator.
I start the search from a content management system called Obtree.
To make a full text search is no problem.
But know i will create a search form for meta tags (for example i will search for author or title). It should be possible to generate extra fields for the meta tags.
Where can I make such a search form and where can i make a script for the query?
Thank´s for help
Astrid (from Salzburg Austria)
When you start having different fields that you are searching you are getting to the point where a full Texis application may be appropriate, rather than just Webinator. For example with full Texis you could create an Author field in the table.
The title is stored in the Title field of the Webinator table. You would need to edit the search script. There is a function "showform" which displays the search form, and a function "search" which actually performs the search. The search already has the option to search by title if you have an input box named tq. You could add something similar to search the Meta field for other meta-tags.
You can create an index on a field so you can search by just that field. Eg:
texis -d /path/to/your/database -s "create metamorph inverted index xmtitle on html(Title)"
You'll have to do that by hand after each walk.
Then you'll have to customize the search script to search by "Title" instead of "Title\Description\Keywords\Meta\Body".
Using Webinator to index pages created by a CMS (content management system) is outside the bounds of acceptable use in most cases. (See last section of the Webinator license agreement.) Users wishing to do this should contact Thunderstone Sales for a special license allowing that.
I have a similar problem, but I would like one of the meta tags to be a date tag (foxdate). What is the best way for the search results to be ordered by foxdate? Will the SQL engine recognize the foxdate meta tag as being a "date" data type and know how to order by foxdate? Or, will it by default sort the results according to how foxdate is ordered as a string?
One option would be to extract the date in the crawler, and store it in the the Visited column, which is a date.
Ordering string fields will use string ordering, with no data type translation.
If you have a significant number of custom meta tags and other information you want to handle specially you want to consider full Texis, which, among other things, lets you customize the schema to your needs.
