Versions Compared

Old Version 2

changes.mady.by.user Bram Luyten (Atmire)

Saved on

compared with

New Version Current

changes.mady.by.user Tim Donohue

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • <element> - the Dublin Core element
  • <qualifier> - the element's qualifier

  • <language>- (optional)ISO language code for element

    Code Block
    <dublin_core>
    <dcvalue element="title" qualifier="none">A Tale of Two Cities</dcvalue>
    <dcvalue element="date" qualifier="issued">1990</dcvalue>
    <dcvalue element="title" qualifier="alternatealternative" language="fr">J'aime les Printemps</dcvalue>
</dublin_core>

    (Note the optional language tag attribute which notifies the system that the optional title is in French.)

Every metadata field used, must be registered via the metadata registry of the DSpace instance first, see Metadata and Bitstream Format Registries.

Note
titleRecommended Metadata

It is recommended to minimally provide "dc.title" and, where applicable, "dc.date.issued".  Obviously you can (and should) provide much more detailed metadata about the Item.  For more information see: Metadata Recommendations.

 

The contents file simply enumerates, one file per line, the bitstream file names. See the following example:

...

Replacing existing items is relatively easy. Remember that mapfile you were supposed to savesaved above? Now you will use it. The command (in short form):

...

You are able to unimport or delete items provided you have the mapfile. Remember that mapfile you were supposed to savesaved above? The command is (in short form):

Code Block
[dspace]/bin/dspace import -e joe@user.com -d -m mapfile

In long form:

Code Block
[dspace]/bin/dspace import --eperson=joe@user.com --delete --mapfile mapfile

...

  • Resume. If, during importing, you have an error and the import is aborted, you can use the --resume (-R) flag that you can try to resume the import where you left off after you fix the error.

Exporting Items

The item exporter can export a single item or a collection of items, and creates a DSpace simple archive for according to the aforementioned format for each item to be exported. The items are exported in a sequential order in which they are retrieved from the database. As a consequence, the sequence numbers of the item subdirectories (item_000, item_001) are not related to DSpace handle or item id's.

Command used:

[dspace]/bin/dspace export

Java class:

org.dspace.app.itemexport.ItemExport

Arguments short and (long) forms:

Description

-t or --type

Type of export. COLLECTION will inform the program you want the whole collection. ITEM will be only the specific item. (You will actually key in the keywords in all caps. See examples below.)

-i or --id

The ID or Handle of the Collection or Item to export.

-d or --dest

The destination of where you want the file of items to be placed. You place the path if necessary.

-n or --number

Sequence number to begin export the items with. Whatever number you give, this will be the name of the first directory created for your export. The layout of the export is the same as you would set your layout for an Import.

-m or --migrate

Export the item/collection for migration. This will remove the handle and metadata that will be re-created in the new instance of DSpace.

-h or --help

Brief Help.

...

Using the -m argument will export the item/collection and also perform the migration step. It will perform the same process that the next section Transferring or Copying Exchanging Content Between Repositories performs. We recommend that section to be read in conjunction with this flag being used.