Ticket #665 (closed defect: fixed)

Opened 9 years ago

Last modified 9 years ago

datestamp in OAI records

Reported by: kjdon Owned by: kjdon
Priority: high Milestone: 2.84 Release
Component: Greenstone2 Runtime Severity: major
Keywords: Cc:

Description

As reported by Mariana Pichinini, 18-12-09.

I explain: where among the metadata reported is a DC.date tag, the OAI server treats this as a datestamp for the register. In common practice, this DC.date metadata means the publishing date for a resource, and since this is a internal resource, it usually is not formatted ISO 8601 compliant; in consequence, when OAI server try to read it, it reports a validation fail (I.e. with Open Archives or validators alike)

I don't know the reason for the OAI server to take this DC.date as a datestamp; AFAIK, the most reliable date to take in such a way is the modified date for a source document, which you can take from the 'lastmodified' metadate, present in doc.xml. This is the date that's got everywhere there is no DC.date tag, and I think this is the only one tag that that date should be read from.

When the collection do not implement Dublin Core in their metadata, there is no such trouble. So this mislead is not always raising...

Change History

Changed 9 years ago by kjdon

  • priority changed from moderate to high
  • status changed from new to assigned

Changed 9 years ago by kjdon

Just noticed in the wiki:  http://wiki.greenstone.org/wiki/index.php/Greenstone_interoperability

Uses lastmodifieddate normally, but will use dc.Date in preference so you can correct it if wrong.

This is another example where I think we need a gs metadata set, which is always there in GLI, where you can add metadata that has special meaning in greenstone.

Changed 9 years ago by kjdon

Here is the official info about the datestamp:  http://www.openarchives.org/OAI/openarchivesprotocol.html#Datestamp

Changed 9 years ago by kjdon

I think I will make it use lastmodifieddate unless there is a gs.OAIDate or some new element which I will invent, in which case it will use that. No using dc.Date anymore.

Changed 9 years ago by kjdon

  • status changed from assigned to closed
  • resolution set to fixed

Uses lastmodified, unless there is a gs.OAIDateStamp metadata which will be used in preference.

Note: See TracTickets for help on using tickets.