Versions Compared

Old Version 5

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 6

changes.mady.by.user Tim Donohue

Saved on

Key

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

...

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.
		collections				-- (Optional) text file that contains the handles of the collections the item will belong to. Optional. Each handle in a row.
								-- Collection in first line will be the owning collection.
        relationships           -- (Optional) If importing Entities, you can specify one or more relationships to create on import
        file_1.doc              -- files to be added as bitstreams to the item.
        file_2.pdf
    item_001/
        dublin_core.xml
        contents
        file_1.png
        ...

...

dublin_core.xml or metadata_[prefix].xml

The dublin_core.xml or metadata_[prefix].xml file has file has the following format, where each metadata element has its own entry within a <dcvalue> tagset. There are currently three tag attributes available in the <dcvalue> tagset:

...

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.

contents file

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

...

'PERMISSIONS'  is text with the following format: -[r|w] 'group name'

'DESCRIPTION' is text of the files description.

Primary is used to specify the primary bitstream.

relationships file

Note

Introduced in 7.1.  Currently the 'relationships'

...

file is only supported on import ('add' mode) of an SAF package.

The optional relationships file enumerates the relationships of this Entity to other Entities (either already in the system, or also specified in your SAF import batch).  This allows entities to be linked to new or existing entities during import. Entities can be linked to other entitiess in this import set by referring to their import subfolder name. Because relationships can only be created for Entities, it can only be used when importing Configurable Entities.

Each line in the file contains a relationship type key and an item identifier in the following format:

Code Block
relation.<relation_key> <handle|uuid|folderName:import_item_folder|schema.element[.qualifier]:value>

The input_item_folder should refer the folder name of another item in this import batch. Example:

Code Block
relation.isAuthorOfPublication 5dace143-1238-4b4f-affb-ed559f9254bb
relation.isAuthorOfPublication 123456789/1123
relation.isOrgUnitOfPublication folderName:item_001
relation.isProjectOfPublication project.identifier.id:123
relation.isProjectOfPublication project.identifier.name:A Name with Spaces

During initial import, new items are stored in a map keyed by the item folder name. Once the initial import is complete, a second pass checks for a 'relationships' manifest file in each folder and creates a relationship of the specified type to the specified item.

Info
titleDon't forget Entities require a "dspace.entity.type" metadata field

Remember, if you are creating new Entities via an SAF package, those Entities MUST specify a "dspace.entity.type" metadata field.  Because this metadata field is in the "dspace" schema, it MUST be specified in a "metadata_dspace.xml", similar to:

Code Block
<dublin_core schema="dspace">
  <dcvalue element="entity" qualifier="type">Publication</dcvalue>
</dublin_core>


Configuring metadata_[prefix].xml for a Different Schema

...

  • eperson
  • Collection ID (either Handle (e.g. 123456789/14) or Database ID (e.g. 2)UUID
  • Source directory where the items reside
  • Mapfile. Since you don't have one, you need to determine where it will be (e.g. /Import/Col_14/mapfile)
    At the command line:

...