Versions Compared

Old Version 1

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 2

changes.mady.by.user Anne Lawrence

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: fix typo

...

For Collections, the following fields are translated to the DIM schema:

DIM Metadata Field

Database field or value

dc.description

'introductory_text' field

dc.description.abstract

'short_description' field

dc.description.tableofcontents

'side_bar_text' field

dc.identifier.uri

Collection's handle

dc.provenance

'provenance_description' field

dc.rights

'copyright_text' field

dc.rights.license

'license' field

dc.title

'name' field

DIM Descriptive Elements for Community objects

For Communities, the following fields are translated to the DIM schema:

DIM Metadata Field

Database field or value

dc.description

'introductory_text' field

dc.description.abstract

'short_description' field

dc.description.tableofcontents

'side_bar_text' field

dc.identifier.uri

Handle of Community

dc.rights

'copyright_text' field

dc.title

'name' field

DIM Descriptive Elements for Site objects

For the Site Object, the following fields are translated to the DIM schema:

Metadata Field

Value

dc.identifier.uri

Handle of Site (format: [handle_prefix]/0)

dc.title

Name of Site (from dspace.cfg 'dspace.name' config)

MODS Schema

By default, all DSpace descriptive metadata (DIM) is also translated into the MODS Schema by utilizing DSpace's MODSDisseminationCrosswalk. DSpace's DIM to MODS crosswalk is defined within your [dspace]/config/crosswalks/mods.properties configuration file. This file allows you to customize the MODS that is included within your AIPs.

...

AIP Technical Metadata for Item

Metadata Field

Value

dc.contributor

Submitter's email address

dc.identifier.uri

Handle of Item

dc.relation.isPartOf

Owning Collection's Handle (as a URN)

dc.relation.isReferencedBy

All other Collection's this item is linked to (Handle URN of each non-owner)

dc.rights.accessRights

"WITHDRAWN" if item is withdrawn

AIP Technical Metadata for Bitstream

Metadata Field

Value

dc.title

Bitstream's name/title

dc.title.alternative

Bitstream's source

dc.description

Bitstream's description

dc.format

Bitstream Format Description

dc.format.medium

Short Name of Format

dc.format.mimetype

MIMEType of Format

dc.format.supportlevel

System Support Level for Format (necessary to recreate Format during restore, if the format isn't know to DSpace by default)

dc.format.internal

Whether Format is internal (necessary to recreate Format during restore, if the format isn't know to DSpace by default)

  • Outstanding Question: Why are we recording the file format support status? That's a DSpace property, rather than an Item property. Do DSpace instances rely on objects to tell them their support status?
    • Possible answer (from Larry Stone): Format support and other properties of the BitstreamFormat are recorded here in case the Item is restored in an empty DSpace that doesn't have that format yet, and the relevant bits of the format entry have to be reconstructed from the AIP. --lcs

AIP Technical Metadata for Collection

Metadata Field

Value

dc.identifier.uri

Handle of Collection

dc.relation.isPartOf

Owning Community's Handle (as a URN)

dc.relation.isReferencedBy

All other Communities this Collection is linked to (Handle URN of each non-owner)

AIP Technical Metadata for Community

Metadata Field

Value

dc.identifier.uri

Handle of Community

dc.relation.isPartOf

Handle of Parent Community (as a URN)

AIP Technical Metadata for Site

Metadata Field

Value

dc.identifier.uri

Site Handle (format: [handle_prefix]/0)

PREMIS Schema

At this point in time, the PREMIS Schema is only used to represent technical metadata about DSpace Bitstreams (i.e. Files). The PREMIS metadata is generated by DSpace's PREMISCrosswalk. Only the PREMIS Object Entity Schema is used.

...

The following Bitstream information is translated into PREMIS for each DSpace Bitstream (file):

Metadata Field

Value

<premis:objectIdentifier>

Contains Bitstream direct URL

<premis:objectCategory>

Always set to "File"

<premis:fixity>

Contains MD5 Checksum of Bitstream

<premis:format>

Contains File Format information of Bistream

<premis:originalName>

Contains original name of file

DSPACE-ROLES Schema

All DSpace Groups and EPeople objects are translated into a custom DSPACE-ROLES XML Schema. This XML Schema is a very simple representation of the underlying DSpace database model for Groups and EPeople. The DSPACE-ROLES Schemas is generated by DSpace's RoleCrosswalk.

...