I figured it out, i changed my handle prefix in my dspace.cfg file to what
the prefix was on the previous instance and tried importing again. To my
surprise it was successful this time around. This is a dev instance so I
can play around and make sure everything works as intended but all seems
good so far.
Thank you for the help!
David K.
On Tuesday, November 27, 2018 at 11:40:02 AM UTC-5, David Kinsley wrote:
>
> Are you using the same handler service in the old and new instance ? yes,
> as far as i know
>
> Is the DNS name of the new instance different from the old ? no, the dns
> name is different from the previous one. We're consolidating 3 dspace
> instances into one so all the imports will have differing DNS names.
>
>
> Is there any workaround for this?
>
>
> Thanks for the help!
>
> David K.
>
> On Tuesday, November 27, 2018 at 10:58:26 AM UTC-5, momeven wrote:
>>
>> The code line where this fails is
>>
>>
>>
>> *public *Item installItem(Context c, InProgressSubmission is,
>> String suppliedHandle) *throws *SQLException,
>> AuthorizeException
>> {
>> Item item = is.getItem();
>> Collection collection = is.getCollection();
>> *try *{
>> *if*(suppliedHandle == *null*)
>> {
>> *identifierService*.register(c, item);
>> }*else*{
>> *identifierService*.register(c, item, suppliedHandle);
>> }
>> } *catch *(IdentifierException e) {
>> *throw new **RuntimeException("Can't create an Identifier!", e);*
>> }
>>
>>
>>
>>
>>
>> Since the item comes from another instance it already has a handle, which
>> the code reads from the ‘handle’ file.
>>
>>
>>
>> Are you using the same handler service in the old and new instance ?
>>
>> Is the DNS name of the new instance different from the old ?
>>
>> I am not sure how the different IdentifierProvider Implementations deal
>> with re-registering existing identifiers
>>
>>
>>
>> Monika
>>
>>
>>
>>
>>
>> --
>>
>> Monika Mevenkamp
>>
>> OIT Princeton University
>>
>> Phone: 609-258-4161
>>
>> Skype: mo-meven
>>
>>
>>
>>
>>
>> *From: *<dspace-c...@googlegroups.com> on behalf of Dkinsley <
>> david.ki...@cnu.edu>
>> *Date: *Tuesday, November 27, 2018 at 10:17 AM
>> *To: *DSpace Community <dspace-c...@googlegroups.com>
>> *Subject: *[dspace-community] java.lang.RuntimeException: Can't create
>> an Identifier!
>>
>>
>>
>> I'm attempting to import records to my DSpace 6.3 instance through
>> command line and am being met with this error:
>>
>>
>>
>> *Adding item from directory 0*
>>
>> * Loading dublin core from
>> /usr/local/dspace/imports/DaSCB.zip/DaSCB_docs/0/dublin_core.xml*
>>
>> * Schema: dc Element: contributor Qualifier: author Value: Jean
>> Rech and Clives S. Leyman*
>>
>> * Schema: dc Element: date Qualifier: accessioned Value:
>> 2008-11-18T00:10:17Z*
>>
>> * Schema: dc Element: date Qualifier: available Value:
>> 2008-11-18T00:10:17Z*
>>
>> * Schema: dc Element: date Qualifier: issued Value:
>> 2008-11-18T00:10:17Z*
>>
>> * Schema: dc Element: identifier Qualifier: uri Value: <my
>> url>/handle/2121/142100*
>>
>> * Schema: dc Element: description Qualifier: provenance Value:
>> Made available in DSpace on 2008-11-18T00:10:17Z (GMT). No. of bitstreams:
>> 1*
>>
>> *A Case Study by Aerospatiale and British Aerospace on the Co.pdf:
>> 3420143 bytes, checksum: 02676b5a4db184e00a4e1907afe30714 (MD5)*
>>
>> * Schema: dc Element: title Qualifier: none Value: A Case Study by
>> Aerospatiale and British Aerospace on the Concorde*
>>
>> * Schema: dc Element: type Qualifier: none Value: Document*
>>
>> * Schema: dc Element: subject Qualifier: categories Value:
>> Dynamics and Systems Control Branch documents (Carey Buttrill)*
>>
>> * Schema: dc Element: contributor Qualifier: corpAuthor Value:
>> AIAA*
>>
>> * Schema: dc Element: identifier Qualifier: sfxLinkoff Value: Y*
>>
>> * Processing contents file:
>> /usr/local/dspace/imports/DaSCB.zip/DaSCB_docs/0/contents*
>>
>> * Bitstream: A Case Study by Aerospatiale and British Aerospace on
>> the Co.pdf Bundle: ORIGINAL*
>>
>> * Bitstream: A Case Study by Aerospatiale and British Aerospace on
>> the Co.pdf.txt Bundle: TEXT*
>>
>> * Bitstream: license.txt Bundle: LICENSE*
>>
>> *Processing handle file: handle*
>>
>> *read handle: '2121/142100'*
>>
>> *java.lang.RuntimeException: Can't create an Identifier!*
>>
>> * at
>> org.dspace.content.InstallItemServiceImpl.installItem(InstallItemServiceImpl.java:74)*
>>
>> * at
>> org.dspace.app.itemimport.ItemImportServiceImpl.addItem(ItemImportServiceImpl.java:516)*
>>
>> * at
>> org.dspace.app.itemimport.ItemImportServiceImpl.addItems(ItemImportServiceImpl.java:338)*
>>
>> * at
>> org.dspace.app.itemimport.ItemImportCLITool.main(ItemImportCLITool.java:375)*
>>
>> * at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)*
>>
>> * at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)*
>>
>> * at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*
>>
>> * at java.lang.reflect.Method.invoke(Method.java:498)*
>>
>> * at
>> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)*
>>
>> * at
>> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)*
>>
>> *Caused by: org.dspace.identifier.IdentifierException: Cannot register
>> identifier: Didn't find a provider that supports this identifier.*
>>
>> * at
>> org.dspace.identifier.IdentifierServiceImpl.register(IdentifierServiceImpl.java:123)*
>>
>> * at
>> org.dspace.content.InstallItemServiceImpl.installItem(InstallItemServiceImpl.java:71)*
>>
>> * ... 9 more*
>>
>> *java.lang.RuntimeException: Can't create an Identifier!*
>>
>>
>>
>>
>>
>> This instance already has over 30,000 records on it from a different
>> dspace instance (version 3.3) and i'm trying to start my next round of
>> imports from yet another dspace instance (this one is version 5.5) but i'm
>> suddenly being met with this error. I've searched for solutions but i
>> haven't found anything useful yet. I'd appreciate any help at all.
>>
>>
>>
>> Thanks
>>
>>
>>
>> --
>> 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 Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to dspace-communi...@googlegroups.com.
>> To post to this group, send email to dspace-...@googlegroups.com.
>> Visit this group at https://groups.google.com/group/dspace-community.
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
--
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.
