Revision as of 15:26, 19 September 2011

This page analyzes the structure of DSpace exports from an uncustomized (i.e. out of the box) DSpace installation.

Collection export

Used the following command (from DSpace user documentation) to export a two-item collection with the handle 123456789-6:

./dspace packager -d -a -t AIP -e <user name> -i 123456789-6 calamy.zip

This results in the export of three zipped packages: one for the collection and one for each of the items:

The extracted contents of each zipped file are shown in this screenshot:

The mets.xml file for the collection is structured as follows:

<mets ID="DSpace_COLLECTION_123456789-6" OBJID="hdl:123456789/6" TYPE="DSpace COLLECTION" PROFILE="http://www.dspace.org/schema/aip/mets_aip_1_0.xsd" xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/standards/mets/mets.xsd">
<metsHdr>
<dmdSec> (contains MODS metadata for collection-level description)
<dmdSec> (contains DSpace Intermediate Metadata (DIM) for collection-level description; all mapped to dc; some overlap with MODS metadata)
<amdSec> (contains information on DSpace users and groups associated with the collection)
<fileSec> (references the collection's logo, if there is one)
<structMap> (links the collection to its logo, if there is one, plus its two child items)
<structMap> (links the collection to the DSpace Community)

<metsHdr>
<dmdSec_1> (contains MODS metadata for item)
<dmdSec_2> (contains DIM metadata for item; all mapped to dc; some overlap with MODS metadata)
<amdSec> (contains rights metadata)
<amdSec> (contains rights metadata)
<amdSec> (contains PREMIS object metadata; rights metadata; DIM metadata for the item)
<amdSec> (contains rights metadata)
<amdSec> (contains PREMIS object metadata; rights metadata; DIM metadata for the licence)
<fileSec> (links the item to the license)
<structMap> (links the bitstream to the logical object)
<structMap> (links the item to the collection)

Requirements:

The digital objects get placed in the objects directory
The license.txt files get placed in the metadata/submissiondocumentation directory; the text is parsed to the <rights> container in the PREMIS metadata. See PREMIS metadata: rights#License-based
The mets.xml files get placed in the metadata/submissionDocumentation directory...hmm, why not put them in the metadata directory?

METS file section	Description/notes
<dmdSec>	DC metadata added during transfer/ingest; SIP-level only
<amdSec>	PREMIS metadata
<fileSec>	Lists all the files in the objects directory of the AIP
<structMap>	Groups the contents in the objects directory of the AIP to reflect the folder structure of the AIP

Question: how do we indicate the relationship between the objects and the DSpace collection-level description (the collection-level mets.xml file?)

@@ Line 50: / Line 50: @@
 == Map the elements of the DSpace AIPs to the Archivematica AIP ==
 *The digital objects get placed in the objects directory
-*The license.txt files get placed in the metadata/submissiondocumentation directory; the text is parsed to the <rights> container in the PREMIS metadata
+*The license.txt files get placed in the metadata/submissiondocumentation directory; the text is parsed to the <rights> container in the PREMIS metadata. See [[PREMIS metadata: rights#License-based]]
 *The mets.xml files get placed in the metadata/submissionDocumentation directory...hmm, why not put them in the metadata directory?