Hello Claudia,
Sorry for another question - now I am getting a null pointer exception
whenever I run something, and it is happening on the line with the
provider, for instance:
try
{
provider.registerOnline(context,
dso,
DOI.SCHEME + doiRow.getDoi());
etc...
Have I missed some configuration item?
Best regards,
Paul
On Fri, Mar 9, 2018 at 4:30 PM, Paul Warner <paulwwar...@gmail.com> wrote:
> Hi Claudia,
>
> Excellent! Thank you!
>
> Best regards,
> Paul
>
> On Fri, Mar 9, 2018 at 4:23 PM, Claudia Jürgen <
> claudia.juer...@tu-dortmund.de> wrote:
>
>> Hi Paul,
>>
>> here is the list:
>> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace-api/
>> src/main/java/org/dspace/identifier/DOIIdentifierProvider.java#L75
>> 7 is the step before registering, setting the local metadata.
>>
>> Hope this helps
>>
>> Claudia Jürgen
>>
>>
>>
>> Am 09.03.2018 um 16:08 schrieb Paul Warner:
>>
>>> Hello Claudia,
>>>
>>> Thanks once again for the super tip. :-) We are running Dspace 6.1, so
>>> I
>>> do need the uuid. I got the list of all uuids from the Dspace rest
>>> interface, and then made this simplified insert:
>>>
>>> insert into doi (doi_id,doi,resource_type_id,r
>>> esource_id,status,dspace_object)
>>> values (nextval('doi_seq'), concat('10.xxxx/namespacesepar
>>> ator-',currval('
>>> doi_seq')),2,null,7,'272017e2-9e50-48de-8385-cb599bbc615f');
>>>
>>> Following your suggestion, I set the status to 7. This seems to make the
>>> items ready for update. But I have not registered them yet, they are not
>>> known to DataCite. How can I find the statuses and their numbers?
>>>
>>> Thanks!
>>>
>>> Best regards,
>>> Paul
>>>
>>>
>>>
>>> On Fri, Mar 9, 2018 at 12:43 PM, Claudia Jürgen <
>>> claudia.juer...@tu-dortmund.de> wrote:
>>>
>>> Hello Paul,
>>>>
>>>> we retrospectively added DOI's to our existing instance and had the same
>>>> problem, only items ingested after the doi service is up and running are
>>>> added to the doi table.
>>>> There is afaik not yet a job to insert existing ones.
>>>>
>>>> We manipulated the db - The usual WARNING, backup and be sure what you
>>>> are doing.
>>>> This was on a 4.2 instance but should work on 5.x, too, on 6 you have
>>>> the uuid.
>>>>
>>>> INSERT into doi (doi_id, doi, resource_type_id, resource_id, status)
>>>> SELECT nextval('doi_seq'),
>>>> concat('YOURPREFIX/YOURNAMESPACESEPERATOR-',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);
>>>>
>>>> Hope this helps
>>>>
>>>> Claudia
>>>>
>>>>
>>>> Am 09.03.2018 um 11:35 schrieb Paul Warner:
>>>>
>>>> Hi,
>>>>>
>>>>> I have 52 items in my dspace test instance, and we now have a contract
>>>>> with
>>>>> DataCite to create dois for our items. I read an old post in which
>>>>> Pascal-Nicolas Becker explained that the new items (those loaded in
>>>>> after
>>>>> the doi configuration is complete) are seen as ready for doi
>>>>> processing.
>>>>> How do I tell Dspace that all my 52 items are 'new', so that they get
>>>>> loaded into the doi table for processing? Right now, when I run the
>>>>> commands, I get these results.
>>>>>
>>>>> dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -u
>>>>> There are no objects in the database whose metadata needs an update.
>>>>> dspace@plmachinenameton:~/dspace_instance> bin/dspace doi-organiser -s
>>>>> There are no objects in the database that could be reserved.
>>>>> dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -r
>>>>> There are no objects in the database that could be registered.
>>>>> dspace@machinename:~/dspace_instance> bin/dspace doi-organiser -d
>>>>> There are no objects in the database that could be deleted.
>>>>>
>>>>> There is nothing in the doi table in Postgres, presumably because only
>>>>> new
>>>>> items are recognized as needing dois.
>>>>>
>>>>> Best regards,
>>>>> Paul
>>>>>
>>>>>
>>>>> --
>>>> Claudia Juergen
>>>> Eldorado
>>>>
>>>> Technische Universität Dortmund
>>>> Universitätsbibliothek
>>>> Vogelpothsweg 76
>>>> 44227 Dortmund
>>>>
>>>> Tel.: +49 231-755 40 43
>>>> Fax: +49 231-755 40 32
>>>> claudia.juer...@tu-dortmund.de
>>>> www.ub.tu-dortmund.de
>>>>
>>>> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie
>>>> ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der
>>>> für
>>>> diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den
>>>> Absender
>>>> und vernichten Sie diese Mail. Vielen Dank.
>>>> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen
>>>> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher
>>>> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung
>>>> eines
>>>> solchen Schriftstücks per Telefax erfolgen.
>>>>
>>>> Important note: The information included in this e-mail is confidential.
>>>> It is solely intended for the recipient. If you are not the intended
>>>> recipient of this e-mail please contact the sender and delete this
>>>> message.
>>>> Thank you. Without prejudice of e-mail correspondence, our statements
>>>> are
>>>> only legally binding when they are made in the conventional written form
>>>> (with personal signature) or when such documents are sent by fax.
>>>>
>>>>
>>>> --
>>>> You received this message because you are subscribed to a topic in the
>>>> Google Groups "DSpace Technical Support" group.
>>>> To unsubscribe from this topic, visit https://groups.google.com/d/to
>>>> pic/dspace-tech/fBwxAlcjPZA/unsubscribe.
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> dspace-tech+unsubscr...@googlegroups.com.
>>>> To post to this group, send email to dspace-tech@googlegroups.com.
>>>> Visit this group at https://groups.google.com/group/dspace-tech.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>>
>> --
>> Claudia Juergen
>> Eldorado
>>
>> Technische Universität Dortmund
>> Universitätsbibliothek
>> Vogelpothsweg 76
>> 44227 Dortmund
>>
>> Tel.: +49 231-755 40 43
>> Fax: +49 231-755 40 32
>> claudia.juer...@tu-dortmund.de
>> www.ub.tu-dortmund.de
>>
>> Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie
>> ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für
>> diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender
>> und vernichten Sie diese Mail. Vielen Dank.
>> Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen
>> ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher
>> Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines
>> solchen Schriftstücks per Telefax erfolgen.
>>
>> Important note: The information included in this e-mail is confidential.
>> It is solely intended for the recipient. If you are not the intended
>> recipient of this e-mail please contact the sender and delete this message.
>> Thank you. Without prejudice of e-mail correspondence, our statements are
>> only legally binding when they are made in the conventional written form
>> (with personal signature) or when such documents are sent by fax.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
