DSpace exports - Revision history

Sallain at 21:44, 11 February 2020

2020-02-11T21:44:44Z

Evelyn: /* Descriptive metadata */

2011-09-29T20:46:17Z

Descriptive metadata

Evelyn at 18:57, 29 September 2011

2011-09-29T18:57:47Z

Evelyn: /* OCR text */

2011-09-29T18:55:03Z

OCR text

Evelyn: /* OCR text */

2011-09-29T18:54:13Z

OCR text

Evelyn at 18:52, 29 September 2011

2011-09-29T18:52:57Z

Evelyn: moved Dspace exports to DSpace exports

2011-09-27T23:03:41Z

moved Dspace exports to DSpace exports

Evelyn at 19:29, 23 September 2011

2011-09-23T19:29:46Z

Evelyn at 18:44, 23 September 2011

2011-09-23T18:44:31Z

Evelyn at 17:03, 22 September 2011

2011-09-22T17:03:53Z

← Older revision		Revision as of 21:44, 11 February 2020
Line 1:		Line 1:
	[[Main Page]] > [[Development]] > [[:Category:Development documentation\|Development documentation]] > DSpace exports		[[Main Page]] > [[Development]] > [[:Category:Development documentation\|Development documentation]] > DSpace exports
		+
		+	<div style="padding: 10px 10px; border: 1px solid black; background-color: #F79086;">This page is no longer being maintained and may contain inaccurate information. Please see the [https://www.archivematica.org/docs/latest/ Archivematica documentation] for up-to-date information. </div> <p>

	=Analysis=		=Analysis=

@@ Line 54: / Line 54: @@
 **The DIM metadata is not intended for use outside of DSpace: according to the DSpace website, "[DIM] is used by XsltCrosswalk. It is called the Intermediate format because it is intended solely as an intermediate stage in XML-translation-based crosswalks. To reiterate, This is an INTERMEDIATE format, it is NOT for exporting or harvesting metadata!" However, in uncustomized DSpace all the metadata in the DIM fields are mapped to DC, so there may be no harm in referencing the DIM metadata in the Archivematica METS file.
-*We should dmdSecs to the Archivematica METS file to link each object to its descriptive metadata in the DSpace METS files (i.e. using mdRef).
+*We should add dmdSecs to the Archivematica METS file to link each object to its descriptive metadata in the DSpace METS files (i.e. using mdRef).
 === Checksums ===

@@ Line 1: / Line 1: @@
 [[Main Page]] > [[Development]] > [[:Category:Development documentation|Development documentation]] > DSpace exports
 This page analyzes the structure of a DSpace collection export from an uncustomized (i.e. out of the box) DSpace installation. See also [[Transfer and SIP creation#Workflow.28DSpace export.29| draft workflow]] for transferring and ingesting DSpace exports.
@@ Line 66: / Line 68: @@
 [[Category:Development documentation]]

← Older revision		Revision as of 18:55, 29 September 2011
Line 36:		Line 36:

	[[File:metsOCR.png\|680px\|thumb\|center\|]]		[[File:metsOCR.png\|680px\|thumb\|center\|]]
		+	</br>
		+	The OCR text file should remain in the objects directory of the AIP.

	=== RightsMD ===		=== RightsMD ===

@@ Line 33: / Line 33: @@
 === OCR text ===
-If the AIP contains a scanned PDF file there will also be an accompanying ocr text file with a filename like ''bitstream_39476.txt''. This text is identified in fileSec of the METS file as TEXT:
+If the AIP contains a scanned PDF file there will also be an accompanying ocr text file with a filename like ''bitstream_39476.txt''. This text is identified in fileSec of the METS file as USE=TEXT:
 [[File:metsOCR.png|680px|thumb|center|]]

← Older revision		Revision as of 18:52, 29 September 2011
Line 30:		Line 30:

	Archivematica should move the license file to the metadata/submissionDocumentation directory; the text can be parsed to the rights entity in the PREMIS metadata. See [[PREMIS metadata: rights#License-based]].		Archivematica should move the license file to the metadata/submissionDocumentation directory; the text can be parsed to the rights entity in the PREMIS metadata. See [[PREMIS metadata: rights#License-based]].
		+
		+	=== OCR text ===
		+
		+	If the AIP contains a scanned PDF file there will also be an accompanying ocr text file with a filename like ''bitstream_39476.txt''. This text is identified in fileSec of the METS file as TEXT:
		+
		+	[[File:metsOCR.png\|680px\|thumb\|center\|]]

	=== RightsMD ===		=== RightsMD ===

← Older revision	Revision as of 23:03, 27 September 2011
(No difference)

@@ Line 3: / Line 3: @@
 This page analyzes the structure of a DSpace collection export from an uncustomized (i.e. out of the box) DSpace installation. See also [[Transfer and SIP creation#Workflow.28DSpace export.29| draft workflow]] for transferring and ingesting DSpace exports.
-Used the following command (from DSpace [http://www.dspace.org/1_7_1Documentation/AIP%20Backup%20and%20Restore.html#AIPBackupandRestore-ExportingAIPHierarchy user documentation]) to export a two-item collection with the handle 123456789-6:
+Used the following command (from DSpace [https://wiki.duraspace.org/display/DSDOC/AIP+Backup+and+Restore#AIPBackupandRestore-ExportingAIPs user documentation]) to export a two-item collection with the handle 123456789-6:
 <pre>./dspace packager -d -a -t AIP -e <user name> -i 123456789-6 calamy.zip</pre>

@@ Line 44: / Line 44: @@
 **The DIM metadata is not intended for use outside of DSpace: according to the DSpace website, "[DIM] is used by XsltCrosswalk. It is called the Intermediate format because it is intended solely as an intermediate stage in XML-translation-based crosswalks. To reiterate, This is an INTERMEDIATE format, it is NOT for exporting or harvesting metadata!" However, in uncustomized DSpace all the metadata in the DIM fields are mapped to DC, so there may be no harm in referencing the DIM metadata in the Archivematica METS file.
-*We should add an <mdRef> to the Archivematica METS file to link each object to its descriptive metadata in the DSpace METS files.
+*We should dmdSecs to the Archivematica METS file to link each object to its descriptive metadata in the DSpace METS files (i.e. using mdRef).
@@ Line 55: / Line 55: @@
 == Collection-level mets files ==
-The collection-level mets file contains MODS and DIM metadata for the collection; the MODS metadata should be linked or added to the Archivematica mets file.
+The collection-level mets file contains MODS and DIM metadata for the collection; the descriptive metadata should be linked to the Archivematica mets file in the dmdSec using mdRef.
 [[Category:Development documentation]]
 __NOTOC__

@@ Line 37: / Line 37: @@
 [[File:rights.png|680px|thumb|center|]]
-This metadata can be added to the PREMIS rights entity in the rightsExtension field. See See [[PREMIS metadata: rights#From_DSpace_METS]]
+This metadata can be added to the PREMIS rights entity in the rightsExtension field. See See [[PREMIS metadata: rights#From_DSpace_METS]].
 === Descriptive metadata ===
 *Each object has two dmdSecs: MODS and [https://wiki.duraspace.org/display/DSPACE/DSpaceIntermediateMetadata DSpace Intermediate Metadata (DIM)].
-**The DIM metadata is not intended for use outside of DSpace: according to the DSpace website, "[DIM] is used by XsltCrosswalk. It is called the Intermediate format because it is intended solely as an intermediate stage in XML-translation-based crosswalks. To reiterate, This is an INTERMEDIATE format, it is NOT for exporting or harvesting metadata!"
+**The DIM metadata is not intended for use outside of DSpace: according to the DSpace website, "[DIM] is used by XsltCrosswalk. It is called the Intermediate format because it is intended solely as an intermediate stage in XML-translation-based crosswalks. To reiterate, This is an INTERMEDIATE format, it is NOT for exporting or harvesting metadata!" However, in uncustomized DSpace all the metadata in the DIM fields are mapped to DC, so there may be no harm in referencing the DIM metadata in the Archivematica METS file.
-*What should we do with the MODS metadata?
-**Leave it in the DSpace METS file and just link the object to its METS file?
+*We should add an <mdRef> to the Archivematica METS file to link each object to its descriptive metadata in the DSpace METS files.
-**Add an <mdRef> to the Archivematica METS file to link each object to its MODS metadata?
 === Checksums ===