As an addition to Claudia's database command. We have a DSpace 6.3
instance and so the command is a little bit different:

INSERT into doi (doi_id, doi, resource_type_id, resource_id, status, 
dspace_object) 
SELECT nextval('doi_seq'), 
concat('YOURPREFIX/YOURNAMESPACESEPARATOR-',currval('doi_seq')), 2, item_id, 7, 
dspace_object
FROM item WHERE in_archive=true and uuid not in (select uuid from doi where 
resource_type_id=2);

Am 22.10.18 um 13:35 schrieb Claudia Jürgen:
> Hello Paul,
>
> once you have configured and your DOI ( these notes are for4.x, 5.x) in
> [dspace]/dspace/config/dspace.cfg
>
>   * identifier.doi.prefix
>   * identifier.doi.namespaceseparator
>   * event.consumer.doi.class
>   * event.consumer.doi.filters
>   * event.dispatcher.default.consumers
>
> [dspace]/config/spring/api/identifier-service.xml
>
>   * bean org.dspace.identifier.DOIIdentifierProvider
>   * bean org.dspace.identifier.doi.DOIConnector
>
> and adjusted the crosswalk
> [dspace]/config/crosswalks/DIM2DataCite.xsl
> You can test the crosswalk with
> [dspace]/bin/dspace dsrun 
> org.dspace.content.crosswalk.XSLTDisseminationCrosswalk DataCite <handle> 
> [output-file]
>
> newly added items will get an entry in the doi table.
> You can check what is in your doi table with
> SELECT * from doi;
>
> If you have already existing items you got to retrospectively create
> the entries in the table.
> We did this by manipulating the database (usual warning about backup):
> 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);
>
> and then running the doi-organiser.
>
> Hope this helps
>
> Claudia Jürgen
>
>
>
> Am 22.10.2018 um 12:55 schrieb Paul Münch:
>> Hello,
>>
>> I figured out that the Proxy configuration is not the problem. Somehow
>> it is not possible to do anything with the 'doi-organiser'. Everytime I
>> tried to reserve, register or update all for test purposes, I got these
>> error message: There are no objects in database that could be ...
>> I configured our DSpace-Instance how descriebed in the documentation.
>> The database connection is fine. Can anybody help me?
>>
>> Thanks in advance and kind regards,
>>
>> Paul Münch
>>
>> Am 19.10.18 um 14:20 schrieb Paul Münch:
>>> Hello,
>>>
>>> we have a problem with the 'doi-organiser'-tool via our proxy server.
>>> All proxy configuration works fine, e.g. OAI, REST or command line
>>> programms like 'wget'. But if we use the 'doi-organiser', we get a
>>> 'Connection timed out'. All DSpace-DOI configuration are successfully
>>> tested on VMs without proxy. So there is no problem.
>>> In our Java environment the proxy parameters are all set and are in use
>>> during the 'doi-organiser' ( I check it with 'jps -lvm' ). Additionally
>>> I added 'System.setProperty(...)' to 'DataCiteConnector.java' - without
>>> success.
>>> I have no idea how to solve this issue and hope someone of you could help.
>>>
>>> Thanks in advance and kind regards,
>>>
>>> Paul Münch
>>>
>
> -- 
> 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. / --
> All messages to this mailing list should adhere to the DuraSpace Code
> of Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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
> <mailto:dspace-tech+unsubscr...@googlegroups.com>.
> To post to this group, send email to dspace-tech@googlegroups.com
> <mailto: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.

-- 
Philipps-Universität Marburg | UB 
Digitale Dienste | Deutschhausstraße 9 | D018
Tel. +49 06421 28-24624  
--

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
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.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to