LOCKSS Integration - Revision history

Sallain at 22:25, 11 February 2020

2020-02-11T22:25:18Z

Hbecker: Move to feature requirements category

2017-03-23T19:36:55Z

Move to feature requirements category

Jhs: fixing display of xml samples

2015-10-22T17:10:26Z

fixing display of xml samples

Evelyn: /* Overview */

2014-10-14T18:12:19Z

Overview

Evelyn at 18:10, 14 October 2014

2014-10-14T18:10:43Z

Hbecker: Add sample pointer files

2014-06-18T22:21:51Z

Add sample pointer files

Show changes

Hbecker: /* Updating Metadata */ POST -> PUT

2014-03-27T22:25:33Z

Updating Metadata: POST -> PUT

Hbecker: /* Technical Details */ clarifying kilobyte size

2014-03-20T23:28:37Z

Technical Details: clarifying kilobyte size

Mjordan: /* Updating Metadata */

2014-03-18T21:47:26Z

Updating Metadata

Mjordan: /* Creating a Resource with an Atom Entry */

2014-03-18T19:43:40Z

Creating a Resource with an Atom Entry

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

	[[Category:Feature requirements]]		[[Category:Feature requirements]]

@@ Line 1: / Line 1: @@
 [[Main Page]] > [[Development]] > [[:Category:Development documentation|Development documentation]] > LOCKSS Integration
 ==Status==
@@ Line 878: / Line 880: @@
 </mets>
 </pre>

@@ Line 212: / Line 212: @@
 The pointer file as it arrives in the storage service, unmodified for LOCKSS.
-<pre class='mw-collapsible mw-collapsed'>
+<pre>
 <mets xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.loc.gov/METS/" xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/standards/mets/version18/mets.xsd">
    <metsHdr CREATEDATE="2014-01-14T14:35:15"/>
@@ Line 313: / Line 311: @@
 The package was smaller than the max file size and therefore unsplit.  The package is fully stored, and the local copy was retained.
-<pre class='mw-collapsible mw-collapsed'>
+<pre>
 <mets xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.loc.gov/METS/" xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/standards/mets/version18/mets.xsd">
    <metsHdr CREATEDATE="2014-01-14T14:35:15"/>
@@ Line 415: / Line 411: @@
 The package was smaller than the max file size and therefore unsplit.  The package is fully stored, and the local copy was deleted.
-<pre class='mw-collapsible mw-collapsed'>
+<pre>
 <mets xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.loc.gov/METS/" xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/standards/mets/version18/mets.xsd">
    <metsHdr CREATEDATE="2014-01-14T14:35:15"/>
@@ Line 555: / Line 549: @@
 The package was larger than the max file size and therefore split into several smaller chunks.  The package is fully stored, and the local copy was retained.
-<pre class='mw-collapsible mw-collapsed'>
+<pre>
 <mets xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.loc.gov/METS/" xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/standards/mets/version18/mets.xsd">
    <metsHdr CREATEDATE="2014-01-14T14:35:15"/>
@@ Line 717: / Line 709: @@
 The package was larger than the max file size and therefore split into several smaller chunks.  The package is fully stored, and the local copy was deleted.
-<pre class='mw-collapsible mw-collapsed'>
+<pre>
 <mets xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns="http://www.loc.gov/METS/" xsi:schemaLocation="http://www.loc.gov/METS/ http://www.loc.gov/standards/mets/version18/mets.xsd">
    <metsHdr CREATEDATE="2014-01-14T14:35:15"/>

@@ Line 12: / Line 12: @@
 LOCKSS (Lots of Copies Keeps Stuff Safe) http://www.lockss.org/ is treated by Archivematica as a storage sub-system.  The Archivematica Storage Service can be configured to store AIPs in a LOCKSS network.  The procedure for storing AIPs follows the SWORD v2 protocol: http://swordapp.org/sword-v2/ .
-The Archivematica Storage Service contains an implementation of a SWORD client, which communicates with a Sword server.  The implementation of the SWORD Server is provided by LOCKSS-O-Matic https://github.com/mjordan/lockss-o-matic.  LOCKSS-O-Matic is responsible for communicating with the Private LOCKSS Network (PLN)
+The Archivematica Storage Service contains an implementation of a SWORD client, which communicates with a SWORD server.  The implementation of the SWORD Server is provided by LOCKSS-O-Matic https://github.com/mjordan/lockss-o-matic.  LOCKSS-O-Matic is responsible for communicating with the Private LOCKSS Network (PLN)
 ===Basic Workflow===

@@ Line 4: / Line 4: @@
 '''Sponsored''': SFU Library<br>
-'''Development Status''': In Progress<br>
+'''Development Status''': Complete<br>
-'''Public Release''': estimated April 2014
+'''Public Release''': September 2014

@@ Line 161: / Line 161: @@
 ===Updating Metadata===
-Archivematica informs LOCKSS-O-Matic that it wants to delete the local copy of a file by POSTing to the SE-IRI an Atom document containing lom:content elements with a recrawl="false" attribute for each file. LOCKSS-O-Matic responsds with a 202 Accepted and updates the LOCKSS configuration files to indicate that the AU the file is in should not be reharvested. After the configuration files have been updated, LOCKSS-O-Matic will respond with a 200 OK to the same request.
+Archivematica informs LOCKSS-O-Matic that it wants to delete the local copy of a file by PUTing to the SE-IRI an Atom document containing lom:content elements with a recrawl="false" attribute for each file. LOCKSS-O-Matic responds with a 202 Accepted and updates the LOCKSS configuration files to indicate that the AU the file is in should not be reharvested. After the configuration files have been updated, LOCKSS-O-Matic will respond with a 200 OK to the same request.
-POST SE-IRI
+PUT SE-IRI
 <pre>
 <?xml version="1.0"?>

@@ Line 47: / Line 47: @@
      <sword:version>2.0</sword:version>
      <!-- maxUploadSize is configurable in LOCKSS-O-Matic. →
-     <!-- measured in kB -->
+     <!-- measured in kB, where kB = 1000*Byte -->
      <sword:maxUploadSize>102400</sword:maxUploadSize>
@@ Line 79: / Line 79: @@
      <author><name>Name of PREMIS agent owning AIP</name></author>
      <summary type="text">The AIP’s dc:description if it has one. If not, use a generic summary.</summary>
      <lom:content size="102400" checksumType="md5" checksumValue="bd4a9b642562547754086de2dab26b7d">
          http://archivematica.example.org/archival-storage/download/aip/dd3e3247-8466-4f2a-bb32-22a210cfce60.001

@@ Line 68: / Line 68: @@
 ===Creating a Resource with an Atom Entry===
-Archivematica issues a POST to the Col-IRI, ensuring that the <id> element in the Atom entry contains the UUID of the AIP:
+Archivematica issues a POST to the Col-IRI, ensuring that the <id> element in the Atom entry contains the UUID of the AIP, and that the URLs to the files to be preserved are listed in lom:content elements:
 <pre>