Page History
...
- Login as an Administrative user
- In Sidebase, select "Export" → "Metadata". Type in the Community/Collection name.
- Alternatively, browse
- to the Community or Collection you wish to export, and
- then go to "Export
- In XMLUI, "Export Metadata" can be found in the "Context" menu on a Community/Collection homepage
- In JSPUI, "Export Metadata" can be found in the "Admin Tools" menu on a Community/Collection homepage
- Or search for items within your repository, and click "Export Metadata" in the search results to export to a downloadable CSV
- In XMLUI, perform a search, and click on "Export Search Metadata" in the "Context" menu. By default, this option is only available to Administrators (
xmlui.search.metadata_export=admin), but you can optionally allow any logged in user to export this metadata (xmlui.search.metadata_export=user), or anyone (xmlui.search.metadata_export=anonymous). - In JSPUI, perform a search, and click on the "Export Metadata" button above the search results.
- In XMLUI, perform a search, and click on "Export Search Metadata" in the "Context" menu. By default, this option is only available to Administrators (
- " → "Metadata". That Community/Collection will be preselected.
- Click "Export". A new Process will be created (in "Processes" menu). Once completed, download the resulting CSV.
| Warning |
|---|
In DSpace 7.0, it is not possible to export to CSV based on search results. This feature existed in 6.x, and it is scheduled to be restored in a later 7.x release (currently 7.1). See DSpace Release 7.0 Status. |
Please see below documentation for more information on the CSV format and actions that can be performed by editing the CSV.
...
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. |
To run the batch editing exporter, at the command line:
...
- First, complete all editing of the CSV and save your changes
- Login as an Administrative User
- Click In sidebar, select "Import" → "Metadata" and select drag & drop the CSV file
| Warning |
|---|
In |
...
DSpace 7.0, metadata import will occur immediately & results will be reported. In 6.x, after uploading the CSV, you |
...
were first presented with a summary of |
...
the changes that |
...
were to be performed |
...
, allowing you to review and choose whether to apply them or cancel. This "preview" feature will be restored in a later 7.x release (currently 7.1), see DSpace Release 7.0 Status. |
Command Line Import
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. |
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.
...
| Info | ||
|---|---|---|
| ||
When editing a CSV, here's a couple of basic tips to keep in mind:
|
...
Editing Collection Membership
...
Overview
Content Tools