[dspace-tech] Advanced search and/or options

2020-03-19 Thread David Kinsley
Morning all, i had a question about the DSpace 6.3 JSPUI advanced search.  
In previous DSpace iterations, users could join advanced search filters 
with AND or OR options but those have seemingly been removed from 6.3.  Is 
there anyway to add them again or have they been removed entirely?

Thanks,
David K.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/8ac0f5da-c0f3-48b9-904b-bcd64c48f8fd%40googlegroups.com.


[dspace-tech] Re: Custom advanced search filters differ after scope change

2020-01-23 Thread David Kinsley
Yep i believe I got the search filters working as well.  I had been running 
the `index-discovery -b` command to reindex everything but that didn't seem 
to be working.  I tried instead `index-discovery -f` and the indices seem 
to showing up when searched for explicitly now.

Thanks for your help!
David K.

On Thursday, January 23, 2020 at 9:16:04 AM UTC-5, Anne Lawrence wrote:
>
> David,
>
> That's great the filters are showing now. Yes, each bean has to be 
> specified separately in discovery.xml. To diagnose the lack of filter 
> results, I would first check the indexing. I believe, when implementing new 
> filters, we have had to force a complete re-indexing to get the facets and 
> filters to show and work properly.
>
> Anne
>
> On Thursday, January 23, 2020 at 9:06:17 AM UTC-5, David Kinsley wrote:
>>
>> Hey Anne, thanks so much for the response.  The custom filters are 
>> showing up when i change the scope now.  In case anyone stumbles upon this 
>> in the future with the same problem, I had to place my custom filters in 
>> the defaultConfiguration bean also, not just the homepageConfiguration.
>>
>> If you don't mind me asking another similar question, i can't get the 
>> custom filters to work; they always return with no produced results.  I've 
>> edited discovery.xml, rebuilt dspace and re-index my handles but i still 
>> can't get the advanced search to return results.  Did i miss a step perhaps?
>>
>> Thanks for the help,
>> David K.
>>
>>
>>
>>
>> On Wednesday, January 22, 2020 at 2:33:59 PM UTC-5, Anne Lawrence wrote:
>>>
>>> We're on DSpace 6.3 and using XMLUI. We've customized our advanced 
>>> search filter list. It works for both the entire repository and specific 
>>> communities. You are welcome to review our code in 
>>> https://github.com/VTUL/vtechworks/blob/vt_6_x_dev/dspace/config/spring/api/discovery.xml
>>> .
>>>
>>>
>>>
>>> On Wednesday, January 15, 2020 at 1:39:08 PM UTC-5, David Kinsley wrote:
>>>>
>>>> I'm on DSpace 6.3 btw
>>>>
>>>> On Wednesday, January 15, 2020 at 11:45:05 AM UTC-5, David Kinsley 
>>>> wrote:
>>>>>
>>>>> Morning all, I've added custom advanced search filters to my dspace 
>>>>> instance which work fine but when i change the scope of the search (e.g. 
>>>>> from All of Dspace to a specific community in the dropdown), my custom 
>>>>> filters change back to the default ones.  Why is that?  Is there any way 
>>>>> to 
>>>>> get the custom filters to show up all the time?  
>>>>>
>>>>> I've added pictures below of what i mean specifically:
>>>>>
>>>>> When the scope is the entire website (e.g. Search equals "All of 
>>>>> ) :
>>>>>
>>>>> [image: full_scope_filters.JPG]
>>>>>
>>>>> When i reduce the scope to a community:
>>>>>
>>>>> [image: filters_reduced_scope.JPG]
>>>>> I did some digging and it works fine so long as the `location` 
>>>>> parameter doesn't point to a specific community in the url.  Is this 
>>>>> working the way it's intended?  I'd appreciate any help!
>>>>>
>>>>> Thanks,
>>>>> David K.
>>>>>
>>>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/32023f2e-39cc-45d1-8c0d-40c616476b8a%40googlegroups.com.


[dspace-tech] Re: Custom advanced search filters differ after scope change

2020-01-23 Thread David Kinsley
Hey Anne, thanks so much for the response.  The custom filters are showing 
up when i change the scope now.  In case anyone stumbles upon this in the 
future with the same problem, I had to place my custom filters in the 
defaultConfiguration bean also, not just the homepageConfiguration.

If you don't mind me asking another similar question, i can't get the 
custom filters to work; they always return with no produced results.  I've 
edited discovery.xml, rebuilt dspace and re-index my handles but i still 
can't get the advanced search to return results.  Did i miss a step perhaps?

Thanks for the help,
David K.




On Wednesday, January 22, 2020 at 2:33:59 PM UTC-5, Anne Lawrence wrote:
>
> We're on DSpace 6.3 and using XMLUI. We've customized our advanced search 
> filter list. It works for both the entire repository and specific 
> communities. You are welcome to review our code in 
> https://github.com/VTUL/vtechworks/blob/vt_6_x_dev/dspace/config/spring/api/discovery.xml
> .
>
>
>
> On Wednesday, January 15, 2020 at 1:39:08 PM UTC-5, David Kinsley wrote:
>>
>> I'm on DSpace 6.3 btw
>>
>> On Wednesday, January 15, 2020 at 11:45:05 AM UTC-5, David Kinsley wrote:
>>>
>>> Morning all, I've added custom advanced search filters to my dspace 
>>> instance which work fine but when i change the scope of the search (e.g. 
>>> from All of Dspace to a specific community in the dropdown), my custom 
>>> filters change back to the default ones.  Why is that?  Is there any way to 
>>> get the custom filters to show up all the time?  
>>>
>>> I've added pictures below of what i mean specifically:
>>>
>>> When the scope is the entire website (e.g. Search equals "All of 
>>> ) :
>>>
>>> [image: full_scope_filters.JPG]
>>>
>>> When i reduce the scope to a community:
>>>
>>> [image: filters_reduced_scope.JPG]
>>> I did some digging and it works fine so long as the `location` parameter 
>>> doesn't point to a specific community in the url.  Is this working the way 
>>> it's intended?  I'd appreciate any help!
>>>
>>> Thanks,
>>> David K.
>>>
>>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/c0176194-6a61-4c31-b030-6f79d79fdd2b%40googlegroups.com.


[dspace-tech] Re: Custom advanced search filters differ after scope change

2020-01-15 Thread David Kinsley
I'm on DSpace 6.3 btw

On Wednesday, January 15, 2020 at 11:45:05 AM UTC-5, David Kinsley wrote:
>
> Morning all, I've added custom advanced search filters to my dspace 
> instance which work fine but when i change the scope of the search (e.g. 
> from All of Dspace to a specific community in the dropdown), my custom 
> filters change back to the default ones.  Why is that?  Is there any way to 
> get the custom filters to show up all the time?  
>
> I've added pictures below of what i mean specifically:
>
> When the scope is the entire website (e.g. Search equals "All of 
> ) :
>
> [image: full_scope_filters.JPG]
>
> When i reduce the scope to a community:
>
> [image: filters_reduced_scope.JPG]
> I did some digging and it works fine so long as the `location` parameter 
> doesn't point to a specific community in the url.  Is this working the way 
> it's intended?  I'd appreciate any help!
>
> Thanks,
> David K.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/0922ad0b-a807-495f-b725-11e499945c1e%40googlegroups.com.


[dspace-tech] Custom advanced search filters differ after scope change

2020-01-15 Thread David Kinsley
Morning all, I've added custom advanced search filters to my dspace 
instance which work fine but when i change the scope of the search (e.g. 
from All of Dspace to a specific community in the dropdown), my custom 
filters change back to the default ones.  Why is that?  Is there any way to 
get the custom filters to show up all the time?  

I've added pictures below of what i mean specifically:

When the scope is the entire website (e.g. Search equals "All of 
) :

[image: full_scope_filters.JPG]

When i reduce the scope to a community:

[image: filters_reduced_scope.JPG]
I did some digging and it works fine so long as the `location` parameter 
doesn't point to a specific community in the url.  Is this working the way 
it's intended?  I'd appreciate any help!

Thanks,
David K.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/7d20c561-a1c8-4611-9c4d-1815e41b8f9d%40googlegroups.com.


[dspace-tech] Dspace 6 + Postgres 12

2020-01-09 Thread David Kinsley
Can Dspace 6 work with Postgres 12 well?  The documentation says Postgres 
9.4+ but I figured I'd ask here to see if anyone has tried this yet.

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 Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/9e2fb3dd-6162-4889-8f71-4f8a69f9cc8b%40googlegroups.com.


Re: [dspace-tech] Running multiple imports (SAF) at once

2019-12-13 Thread David Kinsley
Thanks for the reply Paul, the simultaneous imports of 6000 work without a 
hitch also.

On Thursday, December 12, 2019 at 7:00:47 AM UTC-5, Paul Münch wrote:
>
> Hello,
>
> I can only report experiences from our local test cases. We tested the 
> import in our cluster on two DSpace nodes and ran simultaneously two 
> imports with 600 records on each node. This worked fine, but I can't say 
> more.
>
> Kind regards,
>
> Paul Münch
>
> Am 10.12.19 um 14:43 schrieb David Kinsley:
>
> Hey all, I've been importing a large amount of records over the past 
> couple weeks and was wondering if it was possible to run multiple import 
> commands concurrently.  For example, I'd start an import on 6000 records 
> and immediately after starting that, I'd start another import with the next 
> 6000 records. Would that be possible or would it end up breaking something 
> along the way? 
>
> Thanks for the help,
> David K.
> -- 
> 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 dspac...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/dspace-tech/fe130e7e-d442-4e7b-81b4-a7d8c576a41c%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/dspace-tech/fe130e7e-d442-4e7b-81b4-a7d8c576a41c%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/3124a754-a48e-4d68-85a5-214c415146a1%40googlegroups.com.


[dspace-tech] Running multiple imports (SAF) at once

2019-12-10 Thread David Kinsley
Hey all, I've been importing a large amount of records over the past couple 
weeks and was wondering if it was possible to run multiple import commands 
concurrently.  For example, I'd start an import on 6000 records and 
immediately after starting that, I'd start another import with the next 
6000 records. Would that be possible or would it end up breaking something 
along the way?

Thanks for the help,
David K.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/fe130e7e-d442-4e7b-81b4-a7d8c576a41c%40googlegroups.com.


[dspace-tech] Setting up multiple assetstores on separate machine from dspace

2019-04-01 Thread david . kinsley . 13
I'm running DSpace 6.3 on my server which contains some sensitive records 
that we would like to keep behind a firewall on a separate server than 
where they are currently.  Would it be possible to have DSpace point to, 
and access, the assetstore while it's on a separate machine?  I know you 
can do it on Amazon Web Services (AWS) but i wasn't sure if this was 
restrained to just AWS.  We can't use AWS for the same reason we want to 
move these records behind another firewall-- they're sensitive.  

I appreciate any help you can offer,
David K.

-- 
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.


[dspace-tech] Re: [dspace-community] java.lang.RuntimeException: Can't create an Identifier!

2018-11-27 Thread David Kinsley
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: * on behalf of Dkinsley <
>> david.ki...@cnu.edu>
>> *Date: *Tuesday, November 27, 2018 at 10:17 AM
>> *To: *DSpace Community 
>> *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: > 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*
>>
>&

[dspace-tech] Re: [dspace-community] java.lang.RuntimeException: Can't create an Identifier!

2018-11-27 Thread David Kinsley


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: *> on behalf of 
> Dkinsley >
> *Date: *Tuesday, November 27, 2018 at 10:17 AM
> *To: *DSpace Community >
> *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:  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.dsp