All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
...
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 |
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 |
For the Site Object, the following fields are translated to the DIM schema:
Metadata Field | Value |
---|---|
dc.identifier.uri | Handle of Site (format: |
dc.title | Name of Site (from dspace.cfg 'dspace.name' config) |
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.
...
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 |
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) |
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) |
Metadata Field | Value |
---|---|
dc.identifier.uri | Handle of Community |
dc.relation.isPartOf | Handle of Parent Community (as a URN) |
Metadata Field | Value |
---|---|
dc.identifier.uri | Site Handle (format: |
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 |
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
.
...