Page History
...
The following table summarizes the basics.
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="b6e31581-3b1b-4b50-aeff-7311e34a35ef"><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-version="1" ac:macro-id="258ce34a-60e5-4a05-b33a-081edf756b7e"><ac:plain-text-body><![CDATA[ | ||
| Include all the metadata fields that are not normally changed (e.g. provenance) or those fields you configured in the | ||
| 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. |
...