All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
Wiki Markup |
---|
The _dublin_core.xml_ or _metadata_\[DSDOCDEV: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: |
...
Wiki Markup |
---|
'PERMISSIONS' is text with the following format: -\[r\|DSDOCDEV:w\] 'group name' |
'DESCRIPTION' is text of the files description.
Primary is used to specify the primary bitstream.
Wiki Markup |
---|
Configuring _metadata-\[ |
...
prefix\].xml_ for Different Schema |
It is possible to use other Schema such as EAD, VRA Core, etc. Make sure you have defined the new scheme in the DSpace Metada Schema Registry.
Wiki Markup |
---|
Create a separate file for the other schema named "_metadata-\[DSDOCDEV:prefix\].xml_", where the _\{prefix\}_ is replaced with the schema's prefix. |
Code Block |
---|
<?xml version="1.0" encoding="UTF-8"?> <dublin_core schema="etd"> <dcvalue element="degree" qualifier="department">Computer Science</dcvalue> <dcvalue element="degree" qualifier="level">Masters</dcvalue> <dcvalue element="degree" qualifier="grantor">Texas A & M</dcvalue> </dublin_core> |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="9d9fca7b682639ba-b1775958-493a4f83-8ecdad0e-e96e8a65bb9393c8149a12f7"><ac:plain-text-body><![CDATA[ | Command used: | | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | | ||
Arguments short and (long) forms: | Description | ||
| Add items to DSpace ‡ | ||
| Replace items listed in mapfile ‡ | ||
| Delete items listed in mapfile ‡ | ||
| Source of the items (directory) | ||
| Destination Collection by their Handle or database ID | ||
| Where the mapfile for items can be found (name and directory) | ||
| Email of eperson doing the importing | ||
| Send submission through collection's workflow | ||
| Kicks off the email alerting of the item(s) has(have) been imported | ||
| Test run‚ do not actually import items | ||
| Apply the collection template | ||
| Resume a failed import (Used on Add only) | ||
| Command help |
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7aeedc3bc24a78fd-925eaba4-4d73492e-afc9942e-4be2aa089ad84b5729a0f7af"><ac:plain-text-body><![CDATA[ | Command used: | | ]]></ac:plain-text-body></ac:structured-macro> |
Java class: | org.dspace.app.itemexport.ItemExport | ||
Arguments short and (long) forms: | Description | ||
| 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.) | ||
| The ID or Handle of the Collection or Item to export. | ||
| The destination of where you want the file of items to be placed. You place the path if necessary. | ||
| 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. | ||
| Export the item/collection for migration. This will remove the handle and metadata that will be re-created in the new instance of DSpace. | ||
| Brief Help. |
...