Page History
...
Metadata Field | Value | ||
---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="87203698bf98695b-a1445273-4a084f24-8d33be7c-eaf8ecd5dd5391222c061ff4"><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) |
...
Wiki Markup |
---|
By default, all DSpace descriptive metadata (DIM) is also translated into the [MODS Schema|http://www.loc.gov/standards/mods/] 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. |
...
Code Block |
---|
aip.disseminate.dmd = MODS, DIM |
The MODS metadata is included within your AIP primarily as to support interoperability. It provides a way for other systems to interact with or ingest the AIP ( without needing to understand the DIM Schema). You may choose to disable MODS if you wish, however this may decrease the likelihood that you'd be able to easily ingest your AIPs into a non-DSpace system (unless that non-DSpace system is able to understand the DIM schema). When restoring/ingesting AIPs, DSpace will always first attempt to restore DIM descriptive metadata. Only if no DIM metadata is found, will the MODS metadata be used during a restore.
...
Metadata Field | Value | ||
---|---|---|---|
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="e0c63cae76a810f1-5581aa14-444b47fc-9c6b9e9b-122f3a0da3851833cd019c1a"><ac:plain-text-body><![CDATA[ | dc.identifier.uri | Site Handle (format: | ]]></ac:plain-text-body></ac:structured-macro> |
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.
In the METS structure, PREMIS metadata always appears within a techMD
inside an <mdWrap MDTYPE="PREMIS">
element. PREMIS metadata is always wrapped withn a <premis:premis>
element. For example:
Code Block |
---|
<amdSec ID="amd_2209">
...
<techMD ID="techMD_2210">
<mdWrap MDTYPE="PREMIS">
<premis:premis>
...
</premis:premis>
</mdWrap>
</techMD>
...
</amdSec>
|
Each Bitstream (file) has its own amdSec
within a METS manifest. So, there will be a separate PREMIS techMD
for each Bitstream within a single Item.
By default, PREMIS metadata is always included in AIPs. It is controlled by the following configuration in your dspace.cfg
:
Code Block |
---|
aip.disseminate.techMD = PREMIS, DSPACE-ROLES
|
PREMIS Metadata for Bitstream
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 |