Re: use_doc_date is ignored, file modified date used

Jim <[email protected]>
Newsgroups gmane.comp.web.htdig.general
Message-ID <[email protected]>
On Thu, 12 May 2005, [email protected] wrote:

> We have set
>
> use_doc_date: True
>
> but pages are being ranked by file modified date not by any of the
> metadata dates.  We are using these metadata date tags:
>
> <META NAME="DC.Date.Created" SCHEME="ISO8601" CONTENT="2003-06-16">
> <META NAME="DC.Date.Issued" SCHEME="ISO8601" CONTENT="2003-06-16">
> <META NAME="DC.Date.Modified" SCHEME="ISO8601" CONTENT="2004-08-03">
>
> Why are the metatags being ignored and the file modified date being used
> instead?  This is a problem because the files are part of a content
> management system that serves the pages dynamically, so the file modified
> date is always now (the time of indexing).

What version of ht://Dig are you using? The meta date handling in 3.1.6
is very buggy. If you are using 3.1.6 you will need to apply the
following patch in order to get correct date parsing.

   ftp://ftp.ccsf.org/htdig-patches/3.1.6/metadate.0

In addition there is a typo in some of the meta date related code in
htdig/HTML.cc. On line 96, or thereabouts, the meta name pattern is
defined as follows.

   metadatetags.Pattern("date|dc.date|dc.date.created|dc.data.modified");

The last string specifies 'data' rather than 'date'. Unless you change
the source appropriately your DC.Date.Modified value will be ignored.

Jim


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
ht://Dig general mailing list: <[email protected]>
ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-general
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.