AIP re-ingest - Revision history

Sallain at 22:14, 11 February 2020

2020-02-11T22:14:46Z

2018-05-22T09:32:06Z

techMD: correct superseded vs. current

2018-03-13T15:28:46Z

Use cases

2017-03-23T19:26:48Z

Move to feature requirements category

2016-12-20T18:00:54Z

Use cases

2016-12-10T00:01:35Z

2016-12-09T23:40:18Z

2016-12-09T22:56:11Z

fileSec description

2016-12-09T22:52:20Z

Updates to METS versioning

2016-12-09T22:40:16Z

← Older revision		Revision as of 22:14, 11 February 2020
Line 1:		Line 1:
	[[Main Page]] > [[Requirements]] > AIP re-ingest		[[Main Page]] > [[Requirements]] > AIP re-ingest
		+
		+	<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 requirements for retrieving an Archivematica AIP from archival storage and re-ingesting it for further processing.		This page documents requirements for retrieving an Archivematica AIP from archival storage and re-ingesting it for further processing.

@@ Line 70: / Line 70: @@
 *After re-ingest, the original techMD will contain the PREMIS:Object metadata and the status="superseded."
-*The next techMD will be status="superseded" and contain the PREMIS:Object metadata generated on re-ingest, as well as all PREMIS events from each ingest and re-ingest. This shows the complete set of actions taken upon the objects since they came into the repository.
+*The next techMD will be status="current" and contain the PREMIS:Object metadata generated on re-ingest, as well as all PREMIS events from each ingest and re-ingest. This shows the complete set of actions taken upon the objects since they came into the repository.
 *The timestamp (created="[date/time]") is also updated.

@@ Line 21: / Line 21: @@
 *Rerunning other micro-services (Examine Contents, Transfer Structure Report) (unsponsored)
 *Extracting packages and then deleting the packages (unsponsored)
 ==Full re-ingest==

@@ Line 3: / Line 3: @@
 This page documents requirements for retrieving an Archivematica AIP from archival storage and re-ingesting it for further processing.
 =Use cases=
@@ Line 79: / Line 81: @@
 The fileSec does not indicate its status, but should reflect the files in the AIP currently. For example, if normalization is not performed on the first ingest, but is performed on reingest, the fileSec in the reingested AIP will include preservation derivatives.

@@ Line 11: / Line 11: @@
 *Adding new submission documentation (unsponsored)
 *Adding new digital objects (unsponsored)
-*Deleting digital objects (unsponsored)
+*Deleting original digital objects (unsponsored)
 *Redoing format identification/validation/characterization (version 1.6)
 *Redoing metadata extraction (version 1.6)
@@ Line 18: / Line 18: @@
 *Running OCR on re-ingest (version 1.6)
 *Rerunning other micro-services (Examine Contents, Transfer Structure Report) (unsponsored)
 ==Full re-ingest==

← Older revision		Revision as of 00:01, 10 December 2016
Line 70:		Line 70:

	===rightsMD===		===rightsMD===
		+
		+	*After re-ingest, the original rightsMD will have the status="superseded" and the revised rightsMD will have the status="current".
		+	*The timestamp (created="[date/time]") is also updated.
		+	*Altering either the rights statement or the act(s) will result in a new rightsMD.

	==fileSec==		==fileSec==

@@ Line 56: / Line 56: @@
 *METS file updates will be handled through  <status>, <created> and <groupID> attributes in the various METS sections. See for example Element <dmdSec> at http://www.loc.gov/standards/mets/docs/mets.v1-9.html.
 *This means that there will always only be one AIP METS file, but it will contain both superseded and current metadata and versioning information for all updates.
 ==dmdSec==

← Older revision		Revision as of 22:56, 9 December 2016
Line 74:		Line 74:
	==fileSec==		==fileSec==

		+	The fileSec does not indicate its status, but should reflect the files in the AIP currently. For example, if normalization is not performed on the first ingest, but is performed on reingest, the fileSec in the reingested AIP will include preservation derivatives.



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

← Older revision		Revision as of 22:52, 9 December 2016
Line 59:		Line 59:

	==dmdSec==		==dmdSec==
		+
		+	*The first dmdSec created will be marked as status="original", and updated/revised dmdSecs will be marked as status="updated". The timestamp (created="[date/time]") is also updated.
		+
		+	==amdSec==
		+
		+	===techMD===
		+
		+	*After re-ingest, the original techMD will contain the PREMIS:Object metadata and the status="superseded."
		+	*The next techMD will be status="superseded" and contain the PREMIS:Object metadata generated on re-ingest, as well as all PREMIS events from each ingest and re-ingest. This shows the complete set of actions taken upon the objects since they came into the repository.
		+	*The timestamp (created="[date/time]") is also updated.
		+
		+	===rightsMD===
		+
		+	==fileSec==