The "datestamp" tag content comes from the "lastModified" metadata that
is added automatically by Greenstone when you build a collection. This
lastModified value is obtained from the operating system, and is usually
the last time the file was edited. However, if the file has been copied
(for example if you used the GLI to add the file into your collection)
then the lastModified value will probably be the time the file was copied.
You're right that dc.Date metadata will be used instead of lastModified
for the datestamp tag, if it exists. I think this is to allow you to set
the datestamp value if the automatic (lastModified) value is incorrect.
Greenstone Digital Library and Digitisation Specialists
Mariana Pichinini wrote:
> I found that if the doc.xml have a DC.date metadata, the OAI server
> takes its content as the datestamp (from the OAI protocol). Is this a
> Is clear my former question?
> Thanks again
> Mariana Pichinini escribi□:
>> Could anyone tell me where does the content for the "datestamp" tag
>> came from?
>> I refer to the field the oaiserver lists as response to the Identify,
>> ListIdentifiers, GetRecord and ListRecords request?
>> I am getting quite weird datestamps in that field, for a collection
>> that was generated today. The address of my oaiserver is:
>> Thanks a lot
>> Mariana Pichinini
>> greenstone-devel mailing list
> greenstone-devel mailing list