From: Cutts III, James H. <CuttsJ@mi...> - 2004-09-27 16:52:08
I am trying to a system to allow me to use ht://Dig to do full text
searching of documents while integrating the results with SQL searches.
I've got several questions that I'll post in separate messages so the
threads won't get too tangled.
Returning the meta information I want: I've decided that the best way
for me to correlate the documents with their associated records in my
SQL database is to imbed the SQL's unique identifier in the document.
Using the SQL unique id provides a simpler identifier than the full
document path. The question is how do I put the SQL unique id into the
document in a way that ht://Dig indexes it and I can get it back out.
After reviewing the ht://Dig documentation on the various <META> tags,
(http://www.htdig.org/meta.html), I decided to "abuse" the <META
description> tag as I know that I can get the content of the <META
description> tag back from ht://Dig. What I've done is to put the SQL
unique id and document title in the <META description tag>.
Ex: <META NAME=3D"description" CONTENT=3D"1184: Distribution =
Then by setting the "use_meta_discription: true" in the htdig.conf file,
I can get the contents of the <META description> tag by returning
$(EXCERPT) in my results template.
This is working rather well, but I am not using the <META description>
tag in the traditional manner. Does anyone have any other suggestions
for storing a SQL unique id in documents so that they can be returned by
Thanks so much,
James H. Cutts III
Computer Project Manager
Contracting and Organizational Research Institute
University of Missouri - Columbia
143C Mumford Hall
Phone: (573) 882-6181
Get latest updates about Open Source Projects, Conferences and News.