EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #10148

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

RE: [EP-tech] coin DOI with Datacite

CAUTION: This e-mail originated outside the University of Southampton.

Hi Yuri,
The DataCiteXML export does not have a 'metadataPrefix' specified, so would not normally be listed in the OAI-PMH interface as a supported format.
I guess you have defined a metadataPrefix for it, so it does appear in your OAI-PMH ListMetadataFormats response?

I can see your point - an export format should be a read-only function - I would not expect the behaviour you describe either!

Cheers,
John

-----Original Message-----
From: eprints-tech-request@ecs.soton.ac.uk <eprints-tech-request@ecs.soton.ac.uk> On Behalf Of Yuri
Sent: 18 June 2025 10:54
To: EPrints.org Technical List <eprints-tech@ecs.soton.ac.uk>
Subject: [EP-tech] coin DOI with Datacite

CAUTION: External Message. Use caution opening links and attachments.

CAUTION: This e-mail originated outside the University of Southampton.

CAUTION: This e-mail originated outside the University of Southampton.

https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feprintsug%2FDataCiteDoi%2Fblob%2Ffb9379fd834d5aad7507b8dcbe6d23bc49165a6e%2Flib%2Fplugins%2FEPrints%2FPlugin%2FExport%2FDataCiteXML.pm%23L61&data=05%7C02%7Ceprints-tech%40ecs.soton.ac.uk%7Cd51d6933ce87446456d608ddae4f95bf%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C638858379007002708%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=uQszaEVEJA5Ts%2BIuTdG97V7gKx93cDc9MvMLxz0p5aM%3D&reserved=0

Can someone explain me why this code will try to coin a DOI while exporting the XML? If the DOI coi has failed before, it will fail again.
This is a read operation that became a write operation. This can be triggered easily on oai2 cgi script is something going wrong, thus OAI failing too.

I'm thinking of implementing a filter in oai2 to avoid records without a DOI, do you have some experience on this?

Thanks!