[Dspace-tech] [DSpace-tech]: Export & Import using SAF technique

[Nada Abo Eita]

Dear DSpace Community, 

 I am trying to migrate data from one DSpace instance to another using Simple Archive Format technique (SAF). 

First I export the items from my old DSpace instance using this command: 

./dspace export -t COLLECTION -i collID -d dest_dir -n 1

Then import the items using this command: 

./dspace import -a -e email@admin -c collID -s items_dir -m map file

But importing items isn't fully working. 

The imported items isn't listed under the collection recent submissions. Meanwhile, when I search these items using its handle or Database ID, I can find them. But they don't appear as a recent submissions. 

Does anyone have an idea why this's happening?

For more clarification, please find the attached snapshots. 

[Hilton Gibson]

Hi Nada

Perhaps this will help: http://wiki.lib.sun.ac.za/index.php/SUNScholar/Export_and_Import_Artifacts/Via_Simple_Archive_Format

Cheers

hg

Hilton Gibson

Ubuntu Linux Systems Administrator

JS Gericke Library

Room 1025C

Stellenbosch University

Private Bag X5036

Stellenbosch

7599

South Africa

Tel: +27 21 808 4100 | Cell: +27 84 646 4758

------------------------------------------------------------------------------
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
_______________________________________________
DSpace-tech mailing list
DSpac...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

[Robbins, Seth David]

Hi Nada,

This might help:

I believe recent submissions is tied to date.accessioned by default, which will be exported in SAFs. If you have items in the destination repository more recent than the accession date of the items from the previous instance, the items you’re importing won’t show up in the recently submitted queue as their dates will be set according to the metadata in the export. 

There’s a migrate (-m) option for the exporter, which will cause the handle, date.issued, date.accessioned, date.available, description.provenance, format.extent and format.mimetype to be excluded from the export.  Date issued will be kept if it differs from date.accessioned.

If that won’t work, you could just remove the date accessioned from the metadata files in the exports, a new one will be assigned on import. If you want the date to reflect the date of the migration but want to keep the rest of the aforementioned metadata, that’s probably the easiest way to go about it. 

Thanks,

Seth Robbins  

[Nada Abo-Eita]

Thank you all for your reply,

Seth, I tried to remove accessioned date and then re import it again but still the same problem.

Please note that even I can't browse/search those items, like if I want to browse items by title, nothing appear.  And the weird thing, that I can find items only using their handlers/DB id. 

Any help?

[Nada Abo-Eita]

Hi All,

I just noticed that I have this error in dspace.log: 

2015-01-14 10:00:38,797 ERROR org.dspace.discovery.SolrServiceImpl @ Error while writing item to discovery index: 10576/10556 message:Server at http://tspace.qu.edu.qa:8080/solr/search returned non ok status:500, message:Internal Server Error

org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException: Server at http://tspace.qu.edu.qa:8080/solr/search returned non ok status:500, message:Internal Server Error

at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:385)

at org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:180)

at org.apache.solr.client.solrj.request.AbstractUpdateRequest.process(AbstractUpdateRequest.java:117)

at org.dspace.discovery.SolrServiceImpl.writeDocument(SolrServiceImpl.java:717)

at org.dspace.discovery.SolrServiceImpl.buildDocument(SolrServiceImpl.java:1398)

at org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:215)

at org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:387)

at org.dspace.discovery.IndexClient.main(IndexClient.java:127)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:225)

at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:77)

I think that's why the items doesn't appear in dspace. 

Any idea about this error !

[Mark H. Wood]

On Wed, Jan 14, 2015 at 12:43:00PM +0300, Nada Abo-Eita wrote:
> Hi All,
>
> I just noticed that I have this error in dspace.log:
>

> 2015-01-14 10:00:38,797 ERROR org.dspace.discovery.SolrServiceImpl @ *Error
> while writing item to discovery index:* 10576/10556 message:Server at

> http://tspace.qu.edu.qa:8080/solr/search returned non ok status:500,
> message:Internal Server Error
> org.apache.solr.client.solrj.impl.HttpSolrServer$RemoteSolrException:
> Server at http://tspace.qu.edu.qa:8080/solr/search returned non ok
> status:500, message:Internal Server Error

mwood@mhw ~ $ HEAD http://tspace.qu.edu.qa:8080/solr/search
500 Can't connect to tspace.qu.edu.qa:8080 (Bad hostname)
Content-Type: text/plain
Client-Date: Wed, 14 Jan 2015 14:00:20 GMT
Client-Warning: Internal response

mwood@mhw ~ $ host tspace.qu.edu.qa
Host tspace.qu.edu.qa not found: 3(NXDOMAIN)
mwood@mhw ~ $

There's your problem.

--
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu