Hi Karol,

A CSV file is a spreadsheet format. So, often the best way to open it to remove 
columns is using either Microsoft Excel or OpenOffice / LibreOffice.  You also 
might be able to use Google Sheets.  Just remember though to save the results 
as a CSV.  If you choose to use Excel, there's hints in the docs that detail 
the best way to open the file (as Excel sometimes has difficulty with UTF-8 CSV 
files): 
https://wiki.duraspace.org/display/DSDOC6x/Batch+Metadata+Editing#BatchMetadataEditing-EditingtheCSV

Tim
________________________________
From: Karol S <[email protected]>
Sent: Friday, October 4, 2019 11:05 AM
To: Tim Donohue <[email protected]>
Cc: DSpace Community <[email protected]>
Subject: Re: [dspace-community] Migrate metadata from one collection to another

Tim,

thank you, sounds good. Before my question i didn't need open csv file  (i used 
linux command "sed" to change handle number). Which is the best option to 
delete other columns from csv file? Regards,

Karol

pt., 4 paź 2019 o 16:24 Tim Donohue 
<[email protected]<mailto:[email protected]>> napisał(a):
Hi Karol,

It's hard to say exactly what may be going on.  But, sometimes it helps to 
simplify the CSV you are importing.  So, if they *only* change you want to make 
is to move some Items from one Collection to another, then you should be able 
to delete every column from the CSV *except the 'id' column and 'collection' 
column*  (as any missing columns are ignored).  Then update the 'collection' 
column to the new Collection's handle and do the import.  More info on 
simplifying these CSVs before importing can be found in the docs here (see the 
blue note named "Tips to Simplify the Editing Process"): 
https://wiki.duraspace.org/display/DSDOC6x/Batch+Metadata+Editing#BatchMetadataEditing-EditingtheCSV

If it still isn't working, you may want to also check your DSpace log files to 
see if any error is appearing there when you do the import.

Let us know on this list if you have further questions.

Tim
________________________________
From: 
[email protected]<mailto:[email protected]> 
<[email protected]<mailto:[email protected]>> 
on behalf of Karol S <[email protected]<mailto:[email protected]>>
Sent: Friday, October 4, 2019 8:19 AM
To: DSpace Community 
<[email protected]<mailto:[email protected]>>
Subject: [dspace-community] Migrate metadata from one collection to another

Hi!

Hi, i trying move items from one collection (handle: 1234/10) to another 
collection (handle 1234/20).

I using:

* metadata export from 1234/10 on website ( I exporting csv file)
* i changing handlein csv file from 1234/10 to 1234/20
* /dspace metadata-import -f file.csv

and.... a lot of collections working fine, but i have a few wchich i can't 
fully import for example: i exported 500 items but when i trying import i see 
only 100 items to import( in csv file i see 500 records). Why, what it could be 
wrong?

Thank You,

Karol

--
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 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/d70461a0-cef3-4dda-a8e7-f289b17b34d8%40googlegroups.com<https://groups.google.com/d/msgid/dspace-community/d70461a0-cef3-4dda-a8e7-f289b17b34d8%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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/DM5PR22MB0572AAE8A61FA38FBF7F5B06ED9E0%40DM5PR22MB0572.namprd22.prod.outlook.com.

Reply via email to