Hi Pascal,
On 03/08/15 21:04, Becker, Pascal-Nicolas wrote:
> On 03/08/15 1:48 AM, Andrea Schweer wrote:
>>> On 03/08/15 11:16, Claudia Jürgen wrote:
>>> yes this is right. If you enable the identifier service this will only
>>> cover new items.
>>> Assuming you are using the DataCite Connector, the easiest way would
>>> be to manipulate the database (usual warnings about that) to give the
>>> old items the status of newly items in archive:
>>> INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
>>> SELECT nextval('doi_seq'),
>>>
>>> concat('YOURPREFIX/YOURNAMESPACESEPARATOR-',currval('doi_seq')), 2,
>>> item_id, 7 FROM item WHERE in_archive=true and item_id not in (select
>>> resource_id from doi where resource_type_id=2);
>>>
>>> Then the cron job for the usual doi-organiser commands will pick up the job.
>>>
>>> Perfect, thanks a lot for that!
> It should be easy to add a command in the doi-organiser that adds those
> entries into the database. I just didn't had the use case and the time. ;-)
All good :) It just wasn't obvious to me from the documentation. Perhaps
I'll have the time to change the docs / add this functionality to
doi-organiser, but no promises -- I have the use case but not
necessarily the time...
cheers,
Andrea
--
Dr Andrea Schweer
IRR Technical Specialist, ITS Information Systems
The University of Waikato, Hamilton, New Zealand
------------------------------------------------------------------------------
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
