Page History
...
For information about configuration options for the Batch Metadata Editing tool, see Batch Metadata Editing Configuration
...
| Warning | ||
|---|---|---|
| ||
Out of the box, the batch metadata editing features do not support the DSpace versioning system. Changes are applied straight on the item metadata and no versions of these items are being generated and stored as part of these edit operations. Be careful when using these features. |
User Interface Functionality
Both the XML and JSP user interfaces allow administrator users to:
- Export metadata into a CSV file.
- Import metadata in a CSV, with the goal of modifying existing items or creating new ones.
XML User Interface
Exporting metadata for a particular collection
...screenshot to be added...
Uploading CSV with changes to be processed
...screenshot to be added...
Review and approval of changes
...screenshot to be added...
JSP User Interface
Exporting metadata for a particular collection
...screenshot to be added...
Uploading CSV with changes to be processed
...screenshot to be added...
Review and approval of changes
...screenshot to be added...
Command Line Functionality
Export parameters
The following table summarizes the basics.
Command used: |
|
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. |
| Include all the metadata fields that are not normally changed (e.g. provenance) or those fields you configured in the |
| Display the help page. |
...
Example commands
To run the batch editing exporter, at the command line:
...
In the above example we have requested that a collection, assigned handle '1989.1/24' export the entire collection to the file 'col_14.csv' found in the '/batch_export' directory.
Import
...
parameters
The following table summarizes the basics.
...
Silent Mode should be used carefully. It is possible (and probable) that you can overlay the wrong data and cause irreparable damage to the database.
...
Example commands
To run the batch importer, at the command line:
...
Overview
Content Tools