Page History
...
The following tables describe how various metadata fields schemas are populated (via DSpace Crosswalks) in the METS file for an AIP.
DIM
...
(DSpace Intermediate Metadata) Schema
DIM Schema is essentially a way of representing DSpace internal metadata structure, which is essentially very similar to a Qualified Dublin Core. However, DSpace's metadata allows for custom elements, qualifiers or schemas to be created. These custom fields/schemas may or may not be able to be translated into normal Qualified Dublin Core.
In the METS structure, DIM metadata always appears within a dmdSec
inside an <mdWrap MDTYPE="OTHER" OTHERMDTYPE="DIM">
element.
DIM Descriptive Elements for Item objects
As all DSpace Items already have user-assigned DIM (essentially Qualified Dublin Core) metadata fields, those fields are just exported into the DIM Schema within the METS file.
DIM Descriptive Elements for Collection objects
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
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 Handle of Community |
dc.rights | 'copyright_text' field |
dc.rights.license | 'license' field |
dc.title | 'name' field |
DIM Descriptive Elements for
...
Metadata Field
...
Value
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="6d3223ed-2b2f-483b-8f1c-3b35c6fa7a5f"><ac:plain-text-body><![CDATA[
...
dc.identifier.uri
...
Handle of Site (format: [handle_prefix]/0
)
...
]]></ac:plain-text-body></ac:structured-macro>
...
dc.title
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 | ||
---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="1b281941-81c3-481a-b55a-008688e1c848"><ac:plain-text-body><![CDATA[ | dc.identifier.uri | Handle of Site (format: | ]]></ac:plain-text-body></ac:structured-macro> |
dc.title | Name of Site (from dspace.cfg 'dspace.name' config) |
AIP Technical Metadata Schema (AIP-TECHMD)
The AIP Technical Metadata Schema is a way to translate technical metadata about a DSpace object, into a DIM Schema. It is kept separate from DIM as it is considered technical metadata rather than descriptive metadata.
In the METS structure, AIP-TECHMD metadata always appears within a sourceMD
inside an <mdWrap MDTYPE="OTHER" OTHERMDTYPE="AIP-TECHMD">
element. For example:
Code Block |
---|
<amdSec ID="amd_2191">
...
<sourceMD ID="sourceMD_2198">
<mdWrap MDTYPE="OTHER" OTHERMDTYPE="AIP-TECHMD">
...
</mdWrap>
</sourceMD>
...
</amdSec>
|
...
AIP Technical Metadata for Item
...
Metadata Field | Value | ||
---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="a109b0cb437f8375-15ee4224-4f334600-baec80df-add73ceeef935744d44f4da0"><ac:plain-text-body><![CDATA[ | dc.identifier.uri | Site Handle (format: | ]]></ac:plain-text-body></ac:structured-macro> |