All Versions
- DSpace 7.x (Current Release)
- DSpace 8.x (Unreleased)
- DSpace 6.x (EOL)
- DSpace 5.x (EOL)
- More Versions...
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
...
COMMUNITY_<ID>_ADMIN
group).COLLECTION_<ID>_ADMIN
, COLLECTION_<ID>_SUBMIT
, etc.)....
What is NOT in AIPs
...
...
mets
element @PROFILE
fixed value="http://www.dspace.org/schema/aip/1.0/mets.xsd" (this is how we identify an AIP manifest)@OBJID
URN-format persistent identifier (i.e. Handle) if available, or else a unique identifier. (e.g. "hdl:123456789/1")@LABEL
title if available@TYPE
DSpace object type, one of "DSpace ITEM", "DSpace COLLECTION", "DSpace COMMUNITY" or "DSpace SITE".@ID
is a globally unique identifier, built using the Handle and the Object type (e.g. dspace-COLLECTION-hdl:123456789/3
).mets/metsHdr
element @LASTMODDATE
last-modified date for a DSpace Item, or nothing for other objects.agent
element: @ROLE
= "CUSTODIAN",@TYPE
= "OTHER",@OTHERTYPE
= "DSpace Archive",unmigrated-wiki-markupname
}} = _Site handle_. (Note: The Site Handle is of the format {{\[handle_prefix
\]/0
}}, e.g. "123456789/0")agent
element: @ROLE
= "CREATOR",@TYPE
= "OTHER",@OTHERTYPE
= "DSpace Software",name
= "DSpace \ [version\]" (Where "\[version\]" is the specific version of DSpace software which created this AIP, e.g. "1.7.0")mets/dmdSec
element(s) dmdSec
elements are included for all AIPs: mets/dmdSec/mdWrap@MDTYPE="MODS"
). See #MODS Schema section below for more information.mets/dmdSec/mdWrap@MDTYPE="OTHER",@OTHERMDTYPE="DIM"
. See #DIM (DSpace Intermediate Metadata) Schema section below for more information.mdWrap
@TYPE
value is OTHER
, the element MUST include a value for the @OTHERTYPE
attribute which names the crosswalk that produced (or interprets) that metadata, e.g. DIM
.dmdSec
elements may exist which describe the Item Template for that Collection. Since an Item template is not an actual Item (i.e. it only includes metadata), it is stored within the Collection AIP. The Item Template's dmdSec
elements will be referenced by a div @TYPE="DSpace ITEM Template"
in the METS structMap
.mdWrap
@TYPE
value is OTHER
, the element MUST include a value for the @OTHERTYPE
attribute which names the crosswalk that produced (or interprets) that metadata, e.g. DIM
.mets/amdSec
element(s) amdSec
elements are include for all AIPs. The first amdSec
element contains administrative metadata (technical, source, rights, and provenance) for the entire archival object. Additional amdSec
elements may exist to describe parts of the archival object (e.g. Bitstreams or Bundles in an Item). techMD
elements. By default, two types of techMD
elements may be included: PREMIS
metadata about an object may be included here (currently only specified for Bitstreams (files)). Specified by mdWrap@MDTYPE="PREMIS"
. See #PREMIS Schema section below for more information.DSPACE-ROLES
metadata may appear here to describe the Groups or EPeople related to this object (_currently only specified for Site, Community and Collection). Specified by mdWrap@MDTYPE="OTHER",@OTHERMDTYPE="DSPACE-ROLES"
. See #DSPACE-ROLES Schema section below for more information.rightsMD
elements. By default, there are four possible types of rightsMD
elements which may be included: METSRights
metadata may appear here to describe the permissions on this object. Specified by mdWrap@MDTYPE="OTHER",@OTHERMDTYPE="METSRIGHTS"
. See #METSRights Schema section below for more information.DSpaceDepositLicense
if the object is an Item and it has a deposit license, it is contained here. Specified by mdWrap@MDTYPE="OTHER",@OTHERMDTYPE="DSpaceDepositLicense"
.CreativeCommonsRDF
If the object is an Item with a Creative Commons license expressed in RDF, it is included here. Specified by mdWrap@MDTYPE="OTHER",@OTHERMDTYPE="CreativeCommonsRDF"
.CreativeCommonsText
If the object is an Item with a Creative Commons license in plain text, it is included here. Specified by mdWrap@MDTYPE="OTHER",@OTHERMDTYPE="CreativeCommonsText"
.sourceMD
element. By default, there is only one type of sourceMD
element which may appear: AIP-TECHMD
metadata may appear here. This stores basic technical/source metadata about in object in a DSpace native format. Specified by mdWrap@MDTYPE="OTHER",@OTHERMDTYPE="AIP-TECHMD"
. See #AIP Technical Metadata Schema (AIP-TECHMD) section below for more information.digiprovMD
element. mets/fileSec
element fileGrp
. The fileGrp
has a @USE
attribute which corresponds to the Bundle name.file
elements under fileGrp
.mets/fileSec/fileGrp/file
elements @SIZE
to length of the bitstream. There is a redundant value in the <techMD> but it is more accessible here.@MIMETYPE
, @CHECKSUM
, @CHECKSUMTYPE
to corresponding bitstream values. There is redundant info in the <techMD>. (For DSpace, the @CHECKSUMTYPE="MD5"
at all times)@SEQ
to bitstream's SequenceID if it has one.@ADMID
to the list of <amdSec>
element(s) which describe this bitstream.fileSec
with one fileGrp
child of @USE="LOGO"
.fileGrp
contains one file
element, representing the logo Bitstream. It has the same @MIMETYPE
, @CHECKSUM
, @CHECKSUMTYPE
attributes as the Item content bitstreams, but does NOT include metadata section references (e.g. @ADMID
) or a @SEQ
attribute.structMap
for the fptr
reference to this logo file.mets/structMap
- Primary structure map, @LABEL="DSpace Object", @TYPE="LOGICAL"
div
with @TYPE="DSpace Object Contents"
. div
with @TYPE="DSpace BITSTREAM"
. Each Bitstream div
has a single fptr
element which references the bitstream location.structMap/div/fptr
(i.e. directly under the div
with @TYPE="DSpace Object Contents"
)div
with @TYPE="DSpace Object Contents"
. div
with @TYPE="DSpace ITEM"
. Each Item div
has up to two child mptr
elements: @LOCTYPE="HANDLE"
, and @xlink:href
value is the raw Handle.@LOCTYPE="URL"
, and @xlink:href
value is a relative link to the AIP file on the local filesystem.fptr
reference to it in the very first div
.div
with @TYPE="DSpace ITEM Template"
within the very first div
. This div @TYPE="DSpace ITEM Template"
must have a @DMDID
specified, which links to the dmdSec
element(s) that contain the metadata for the Item Template.div
with @TYPE="DSpace Object Contents"
. div
with @TYPE="DSpace COMMUNITY"
. Each Community div
has up to two mptr
elements: @LOCTYPE="HANDLE"
, and @xlink:href
value is the raw Handle.@LOCTYPE="URL"
, and @xlink:href
value is a relative link to the AIP file on the local filesystem.div
with @TYPE="DSpace COLLECTION"
. Each Collection div
has up to two mptr
elements: @LOCTYPE="HANDLE"
, and @xlink:href
value is the raw Handle.@LOCTYPE="URL"
, and @xlink:href
value is a relative link to the AIP file on the local filesystem.fptr
reference to it in the very first div
.div
with @TYPE="DSpace Object Contents"
. div
with @TYPE="DSpace COMMUNITY"
. Each Item div
has up to two child mptr
elements: @LOCTYPE="HANDLE"
, and @xlink:href
value is the raw Handle.@LOCTYPE="URL"
, and @xlink:href
value is a relative link to the AIP file on the local filesystem.mets/structMap
- Structure Map to indicate object's Parent, @LABEL="Parent", @TYPE="LOGICAL"
div
element which has the unique attribute value TYPE="AIP Parent Link"
to identify it as the older of the parent pointer. mptr
element whose xlink:href
attribute value is the raw Handle of the parent object, e.g. 1721.1/4321
....
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="dd9a3684-ea8f-4177-bd48-a21370c79b14"><ac:plain-text-body><![CDATA[ | dc.identifier.uri | Handle of Site (format: | ]]></ac:plain-text-body></ac:structured-macro> |
dc.identifier.uri | Handle of Site (format: | ||
dc.title | Name | 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|http://www.loc.gov/standards/mods/] by utilizing DSpace's {{ Wiki Markup 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.
For more information on the MODS Schema, see http://www.loc.gov/standards/mods/mods-schemas.html
In the METS structure, MODS metadata always appears within a dmdSec
inside an <mdWrap MDTYPE="MODS">
element. For example:
...
Metadata Field | Value |
---|---|
dc.identifier.uri | Handle of Community |
dc.relation.isPartOf | Handle of Parent Community (as a URN) |
isPartOf | Handle of Parent Community (as a URN) |
Metadata Field | Value | |
---|---|---|
Metadata Field | Value | |
dc.identifier.uri | Site Handle (format: | ]]></ac:plain-text-body></ac:structured-macro> |
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.
...
Info | ||
---|---|---|
| ||
You may have noticed several odd looking group names in the above example, where a Handle is embedded in the name (e.g. "COLLECTION_hdl:123456789/57_SUBMIT"). This is a translation of a Group name which included a Community or Collection Internal ID (e.g. "COLLECTION_45_SUBMIT"). Since you are exporting these Groups outside of DSpace, the Internal ID may no longer be valid or be understandable. Therefore, before export, these Group names are all translated to include an externally understandable identifier, in the form of a Handle. If you use this AIP to restore your groups later, they will be translated back to the normal DSpace format (i.e. the handle will be translated back to the new Internal ID).will be translated back to the new Internal ID). |
Warning | ||
---|---|---|
| ||
Warning | ||
| ||
Groups which are no longer utilized by the system may not be exported in the AIP. If a Group name includes a Community or Collection Internal ID (e.g. "COLLECTION_45_SUBMIT"), and that Community or Collection no longer exists, then the Group will not be exported in any AIPbe renamed to a more generic, random name of the format: "GROUP_[random-hex-key]_[object-type]_[group-type]" (e.g. "GROUP_123eb3a_COLLECTION_ADMIN"). The reasoning is that we were unable to translate an Internal ID into an External ID (i.e. Handle). If we are unable to do that translation, re-importing or restoring a group with an old internal ID could cause conflicts or instability in your DSpace system. In order to avoid such conflicts, these groups will never be included within AIPsare renamed using a random, unique key. |
...