> > > > 1) Create an .html file for each file you need to index, each file to > > contain metadata for indexing and a link to the file it refers to. Then > > index these files. Not a very good solution as far as end-users are > > concerned, but simple to do. > > Ok. Thats fairly similar to my first idea. I will use this solution > only if there is really no alternative. > > > 2) Write a converter script which will add the appropriate metadata > > to the output from doc2html.pl or whatever conversion script you are > > using, during the indexing process. A bit of challenge to write, but > > it should give you exactly what you want and will be transparent to > > end users. > > Yes. But the problem is: How does the script get the metadata? I > would write a wrapper for doc2html.pl, that means that i have no > chance to detect which file htdig requested from the http server, > isn't it? > > > --Nikolaus
Personally I would modify doc2html.pl rather than use a wrapper script, but the method would be similar. You need to create some sort of database (anything from flatfile to Oracle table - whatever suits you) which contains the metadata for each document, with the document URL as the key field. Htdig passes the URL as the second argument to doc2html.pl, so it can look up each document in your database as it is presented for conversion and can insert your metadata in the appropriate place in its output. Bingo! -- David Adams Information Systems Services Southampton University ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
