All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
DSpace provides a batch metadata editing tool. The batch editing tool is able to produce a comma delimited file in the CVS CSV format. The batch editing tool facilitates the user to perform the following:
...
The following table summarizes the basics.
...
Command used: |
| ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.app.bulkedit.MetadataExport | |
Arguments short and (long) forms): | Description | |
| Required. The filename of the resulting CSV. | |
| The Item, Collection, or Community handle or Database ID to export. If not specified, all items will be exported. | |
<ac:structured | Include all the metadata fields that are not normally changed (e.g. provenance) or those fields you configured in the | |
| Display the help page. |
...
In the above example we have requested that a collection, assigned handle '1989.1/24' export the entire collection to the file 'col_14.cvscsv' found in the '/batch_export' directory.
...
The following table summarizes the basics.
...
Command used: |
| ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.app.bulkedit.MetadataImport | |
Arguments short and (long) forms: | Description | |
| Required. The filename of the CSV file to load. | |
| Silent mode. The import function does not prompt you to make sure you wish to make the changes. | |
| The email address of the user. This is only required when adding new items. | |
| When adding new items, the program will queue the items up to use the Collection Workflow processes. | |
| when adding new items using a workflow, send notification emails. | |
| When adding new items, use the Collection template, if it exists. | |
| Display the brief help page. |
...
Code Block |
---|
[dspace]/bin/dspace/ metadata-import -f /dImport/new_file.csv -e joe@user.com -w -n -t |
...
If an action makes no change (for example, asking to withdraw an item that is already withdrawn) then, just like metadata that has not changed, this will be ignored.
...
It is possible that you have data in one Dublin Core (DC) element and you wish to really have it in another. An example would be that your staff have input Library of Congress Subject Headings in the Subject field (dc.subject) instead of the LCSH field (dc.subject.lcsh). Follow these steps and your data is migrated upon import:
Metadata values in CSV export seem to have duplicate columns