EPrints Technical Mailing List Archive
Message: #08172
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] OAI-PMH datestamp value
- To: "eprints-tech@ecs.soton.ac.uk" <eprints-tech@ecs.soton.ac.uk>, "Michael Eadie" <Michael.Eadie@glasgow.ac.uk>
- Subject: Re: [EP-tech] OAI-PMH datestamp value
- From: John Salter <J.Salter@leeds.ac.uk>
- Date: Fri, 15 May 2020 09:27:15 +0000
Hi Mick, In OAI-PMH terms, the 'datestamp' should be when the record was last updated. This is correct - and the basis of the OAI-PMH incremental harvesting. The 'datestamp' in normal EPrints terms is the date that the record was first made live. I think there should be a difference between what CORE see as 'data bout the OAI-PMH representation' and 'data about the item tiself'. Can you see data in CORE that looks incorrect? Cheers, John From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk]
On Behalf Of Michael Eadie via Eprints-tech Hi list I’m looking at out OAI export and the datestamp value, e.g. http://eprints.gla.ac.uk/cgi/oai2?verb=ListRecords&metadataPrefix=oai_dc I had thought datestamp in the export mapped to eprint->datestamp But looking at this in relation to REF work and data we’re sending to Jisc-Core is seems to be ‘date last modified’ that’s being used. Is this the default mapping in EPrints?
Regards Mick |
- Follow-Ups:
- Re: [EP-tech] OAI-PMH datestamp value
- From: John Salter <J.Salter@leeds.ac.uk>
- Re: [EP-tech] OAI-PMH datestamp value
- References:
- [EP-tech] OAI-PMH datestamp value
- From: Michael Eadie <Michael.Eadie@glasgow.ac.uk>
- Re: [EP-tech] OAI-PMH datestamp value
- From: John Salter <J.Salter@leeds.ac.uk>
- [EP-tech] OAI-PMH datestamp value
- Prev by Date: [EP-tech] OAI-PMH datestamp value
- Next by Date: [EP-tech] EPrints / Accessibility / 3.3.17
- Previous by thread: [EP-tech] Sort view with creators_name and corp_creators
- Index(es):