Page History
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
Batch Metadata Editing Tool
...
The following table summarizes the basics.
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="79375c97-cc23-47b3-8f3c-37d1950ec7c6"><ac:plain-text-body><![CDATA[ | 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-macro ac:name="unmigrated-wiki-markup" ac:schema | Include all the metadata fields that are not normally changed (e.g. provenance) or those fields you configured in the | ||
]]></ac:plain-text-body></ac:structured | Display the help page. |
...
The following table summarizes the basics.
...
Command used: |
|
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.
Migrating Data or Exchanging data
...
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:
- Insert a new column. The first row should be the new metadata element. (We will refer to it as the TARGET)
- Select the column/rows of the data you wish to change. (We will refer to it as the SOURCE)
- Cut and paste this data into the new column (TARGET) you created in Step 1.
- Leave the column (SOURCE) you just cut and pasted from empty. Do not delete it.
Common Issues
Metadata values in CSV export seem to have duplicate columns