Page tree

Unreleased Documentation

This documentation is unreleased and still in development. It may describe features which are not yet released in DSpace.
Looking for another version? See all documentation

Skip to end of metadata
Go to start of metadata

The Batch Metadata Editing Tool allows the administrator to extract from the DSpace database a set of records for editing via a CSV file. It provides an easier way of editing large collections.

A full list of all available Batch Metadata Editing Configurations:

Configuration File:

[dspace]/config/modules/bulkedit.cfg

Property:

bulkedit.valueseparator

Example Value:

bulkedit.valueseparator = ||

Informational note

The delimiter used to separate values within a single field. For example, this will place the double pipe between multiple authors appearing in one record (Smith, William || Johannsen, Susan). This applies to any metadata field that appears more than once in a record. The user can change this to another character.

Property:

bulkedit.fieldseparator

Example Value:

bulkedit.fieldseparator = ,

Informational note

The delimiter used to separate fields (defaults to a comma for CSV). Again, the user could change it something like '$'. If you wish to use a tab, semicolon, or hash (#) sign as the delimiter, set the value to be tab, semicolon or hash.

bulkedit.fieldseparator = tab

Property:

bulkedit.authorityseparator

Example Value:

bulkedit.authorityseparator = ::

Informational note

The delimiter used to separate authority data (defaults to a double colon ::)

Property:

bulkedit.gui-item-limit

Example Value:

bulkedit.gui-item-limit = 20

Informational note

When using the WEBUI, this sets the limit of the number of items allowed to be edited in one processing. There is no limit when using the CLI.

Property:

bulkedit.ignore-on-export

Example Value:

bulkedit.ignore-on-export = dc.date.accessioned, \
                            dc.date.available, \
                            dc.date.updated, dc.description.provenance

Informational note

Metadata elements to exclude when exporting via the user interfaces, or when using the command line version and not using the -a (all) option.

Property:

bulkedit.allowexpunge

Example Value:

bulkedit.allowexpunge = false

Informational noteShould the 'action' column allow the 'expunge' method. By default this is set to false
Propertybulkedit.allow-bulk-deletion
Example Value:bulkedit.allow-bulk-deletion = dspace.agreements.end-user
Informational noteComma separated list of metadata fields that can be deleted in bulk using the 'metadata-deletion' script.  By default only the 'dspace.agreements.end-user' field can be deleted in bulk, as doing so allows an Administrator to force all users to re-review the End User Agreement on their next login.  However, you may choose to enable additional fields.  Keep in mind, any fields listed here may be batch deleted from the Processes UI & such metadata deletions cannot be undone.
  • No labels