TRIM exports - Revision history

Sallain at 22:28, 11 February 2020

2020-02-11T22:28:31Z

2017-03-23T19:43:36Z

Move to feature requirements category

2013-02-15T01:15:25Z

Document metadata mapping

2013-02-15T01:15:06Z

Container metadata mapping

2013-01-28T21:42:08Z

2013-01-11T20:51:17Z

Container metadata mapping

2013-01-11T20:47:57Z

Container metadata mapping

2013-01-11T20:47:02Z

Container metadata mapping

2013-01-10T14:34:25Z

Container metadata mapping

2013-01-10T14:30:47Z

TRIM fixity check

← Older revision		Revision as of 22:28, 11 February 2020
Line 1:		Line 1:
	[[Main Page]] > [[Development]] > [[:Category:Development documentation\|Development documentation]] > TRIM exports		[[Main Page]] > [[Development]] > [[:Category:Development documentation\|Development documentation]] > TRIM 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>

	This page documents ingest of TRIM exports based on requirements for VanDocs ingest at City of Vancouver Archives.		This page documents ingest of TRIM exports based on requirements for VanDocs ingest at City of Vancouver Archives.

@@ Line 3: / Line 3: @@
 This page documents ingest of TRIM exports based on requirements for VanDocs ingest at City of Vancouver Archives.
-</br>
+[[Category:Feature requirements]]
 ==TRIM export contents==
@@ Line 389: / Line 389: @@
 *Upon DIP upload to AtoM, the container will become a file-level description, with level of description populated by the structMap div label for the container ("file"). Each object in the DIP will become a child level with the level of description populated by the structMap div label for the object ("item").
 *Descriptive metadata in RAD will be populated by the appropriate dmdSec for each container and object (see container and document metadata mapping, above).

@@ Line 331: / Line 331: @@
 |-
 |n/a
-|'''Level of description''': item
+|'''Level of description''': Item
 |}

@@ Line 270: / Line 270: @@
 |-
 |n/a
-|'''Level of description''': file
+|'''Level of description''': File
 |-
 |'''<FullClassificationNumber>'''04-4000-20

← Older revision		Revision as of 21:42, 28 January 2013
Line 384:		Line 384:

	[[File:VanDocs_rights.png\|680px\|thumb\|center\|]]		[[File:VanDocs_rights.png\|680px\|thumb\|center\|]]
		+
		+	==DIP upload==
		+
		+	*Upon DIP upload to AtoM, the container will become a file-level description, with level of description populated by the structMap div label for the container ("file"). Each object in the DIP will become a child level with the level of description populated by the structMap div label for the object ("item").
		+	*Descriptive metadata in RAD will be populated by the appropriate dmdSec for each container and object (see container and document metadata mapping, above).

	[[Category:Development documentation]]		[[Category:Development documentation]]

@@ Line 272: / Line 272: @@
 |'''Level of description''': file
 |-
-|'''<FullClassificationNumber>'''16-1000-40'''</FullClassificationNumber>'''
+|'''<FullClassificationNumber>'''04-4000-20'''</FullClassificationNumber>'''
+|
 |-

@@ Line 233: / Line 233: @@
 |'''Level of description'''
 |Level of description taken from METS structMap div TYPE
 |}

@@ Line 118: / Line 118: @@
 </br>
-==TRIM fixity check==
+==Fixity check==
 {| border="1" cellpadding="10" cellspacing="0" width=90%