EPrints Technical Mailing List Archive
Message: #00683
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
[EP-tech] Re: datacite, DOI
- To: eprints-tech@ecs.soton.ac.uk
- Subject: [EP-tech] Re: datacite, DOI
- From: raffaele messuti <raffaele.messuti@gmail.com>
- Date: Wed, 6 Jun 2012 14:48:11 +0200
On Wed, Jun 6, 2012 at 2:01 PM, Tim Brody <tdb2@ecs.soton.ac.uk> wrote: > I suspect you only want to update the DOI metadata for live eprint items > and you may want to only create a DOI when the item goes live > (eprint_status_changed). not yet sure about the workflow, we are thinking on it. only admin or editor users should create the identifier, but sometimes they may need to know the identifier before publishing the eprint, to update the document colophon or title page. > EPrints::DataObj::EventQueue->create_unique( > $session, > { > pluginid => "Event::DataCite", > action => "update_metadata", > params => [$eprint->internal_uri], > } > ); > > Then update_metadata() will be called on your Event::DataCite plugin by > the indexer process with the eprint object as its only argument. fine, thank you. my main doubt now is how the event decide when call the update api, i should keep a timestamp when datacite was updated last time? i think i could have solution to this watching how oaipmh works when called with from argument. ciao -- raffaele
- References:
- [EP-tech] Re: datacite, DOI
- From: Tim Brody <tdb2@ecs.soton.ac.uk>
- [EP-tech] datacite, DOI
- From: raffaele messuti <raffaele.messuti@gmail.com>
- [EP-tech] Re: datacite, DOI
- Prev by Date: [EP-tech] Re: datacite, DOI
- Next by Date: [EP-tech] Re: adding a dark archive
- Previous by thread: [EP-tech] Re: datacite, DOI
- Next by thread: [EP-tech] Re: Eprints 3.2 with Preservation plugin (File Formats and Risk Analysis)
- Index(es):