Page History

...

Code Block

archive_directory/
    item_000/
        dublin_core.xml         -- qualified Dublin Core metadata for metadata fields belonging to the dc schema
        metadata_[prefix].xml   -- metadata in another schema, the prefix is the name of the schema as registered with the metadata registry
        contents                -- text file containing one line per filename
        file_1.doc              -- files to be added as bitstreams to the item
        file_2.pdf
    item_001/
        dublin_core.xml
        contents
        file_1.png
        ...

Wiki Markup

The _{{dublin_core.xml_}} or _{{metadata_\[prefix\].xml_}} file has the following format, where each metadata element has it's own entry within a _{{<dcvalue>_}} tagset. There are currently three tag attributes available in the _{{<dcvalue>_}} tagset:

<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="alternate" 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.

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

Code Block
file_1.doc file_2.pdf license

Please notice that the license is optional, and if you wish to have one included, you can place the file in the .../item_001/ directory, for example.

The bitstream name may optionally be followed by any of the following:

\tbundle:BUNDLENAME
\tpermissions:PERMISSIONS
\tdescription:DESCRIPTION
\tprimary:true

Where '\t' is the tab character.

...

Wiki Markup
'PERMISSIONS'  is text with the following format: {{-\[r\\|w\] 'group name'}}

'DESCRIPTION' is text of the files description.

...

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="a8a319a97b7bf6ce-404a3599-41a740d9-b8ed8db9-98b89ac3207a2f02a83f13ca"><ac:plain-text-body><![CDATA[	Command used:	`[dspace]/bin/dspace import`	]]></ac:plain-text-body></ac:structured-macro>
Java class:	`org.dspace.app.itemimport.ItemImport`
Arguments short and (long) forms:	Description
`-a or --add`	Add items to DSpace ‡
`-r or --replace`	Replace items listed in mapfile ‡
`-d or --delete`	Delete items listed in mapfile ‡
`-s or --source`	Source of the items (directory)
`-c or --collection`	Destination Collection by their Handle or database ID
`-m or --mapfile`	Where the mapfile for items can be found (name and directory)
`-e or --eperson`	Email of eperson doing the importing
`-w or --workflow`	Send submission through collection's workflow
`-n or --notify`	Kicks off the email alerting of the item(s) has(have) been imported
`-t or --test`	Test run‚ do not actually import items
`-p or --template`	Apply the collection template
`-R or --resume`	Resume a failed import (Used on Add only)
`-h or --help`	Command help

...

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="ed56cf1505f48006-df198179-497a4bc9-8c0594ee-b836d6178476c80311803128"><ac:plain-text-body><![CDATA[	Command used:	`[dspace]/bin/dspace export`	]]></ac:plain-text-body></ac:structured-macro>
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.

...

All Versions

DSpace Documentation

Page tree

Versions Compared

Old Version 5

New Version 6

Key