Storage API - Revision history

Sallain at 22:03, 11 February 2020

2020-02-11T22:03:19Z

Hbecker: Added proposed changes section

2014-01-22T20:17:43Z

Added proposed changes section

Hbecker: /* Initial Research */ More on how Archivematica touches FS

2013-06-04T22:18:59Z

Initial Research: More on how Archivematica touches FS

Hbecker: /* Initial Research */ More categories

2013-06-04T20:13:57Z

Initial Research: More categories

Hbecker: /* Initial Research */ More on how Archivematica touches FS

2013-06-04T18:15:25Z

Initial Research: More on how Archivematica touches FS

Hbecker: More archivematica and filesystem

2013-06-03T23:56:21Z

More archivematica and filesystem

Hbecker: Ways Archivematica can touch the filesystem start

2013-06-03T23:48:30Z

Ways Archivematica can touch the filesystem start

Hbecker: Initial setup, stub

2013-06-03T23:25:10Z

Initial setup, stub

New page

This is the discussion page for the Archivematica Storage API (Issue #5158), requirements, and proposed implementations.

== Initial Research ==

Goal: Look at all the places Archivematica currently accesses the filesystem, and categorize them.

Likely Categories:
* Transfers
* AIP Storage
* Backlog transfer
* Processing

[[Category:Development documentation]]

← Older revision		Revision as of 22:03, 11 February 2020
Line 1:		Line 1:
		+	<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 is the discussion page for the Archivematica Storage API (Issue #5158), requirements, and proposed implementations.		This is the discussion page for the Archivematica Storage API (Issue #5158), requirements, and proposed implementations.

@@ Line 14: / Line 14: @@
 Categories:
 * Transfers
-** dashboard.... ? , puts in watched directory
+** Starting transfer, puts in watched directory according to transfer type
 * Quarantine
 ** copied to watchedDirectories/quarantined/
 * Backlog transfer
 ** Send to backlog (MicroServiceChainLink abd6d60c-d50f-4660-a189-ac1b34fafe85)
-** Where retrieve from backlog?
+** Retrieve from backlog through create SIP search, or SIP Arrangement (planned)
 * Currently Processing
 ** Anything initiated by putting files in a watchedDirectory, anything being processed by a MicroServiceChain
 ** touched everywhere, in all the client scripts, with python and client scripts.
-** Probably best to keep local
+** Probably best to keep local to Archivematica
 ** Already set up to be move-able with %sharedDirectory% as long as folder structure inside %sharedDirectory% is preserved
 * AIP Storage
@@ Line 30: / Line 30: @@
 Ways Archivematica can touch the filesystem:
 * python's open(), shutil.{move|copy|rm}
 ** mostly just in currently processing
@@ Line 41: / Line 42: @@
 ** dashboard.components.main.models.py SourceDirectory, StorageDirectory
 [[Category:Development documentation]]

@@ Line 1: / Line 1: @@
 This is the discussion page for the Archivematica Storage API (Issue #5158), requirements, and proposed implementations.
 == Initial Research ==
@@ Line 6: / Line 13: @@
 Categories:
 * Transfers
 * Quarantine
 * Backlog transfer
 * Currently Processing
 ** Anything initiated by putting files in a watchedDirectory, anything being processed by a MicroServiceChain
@@ Line 16: / Line 27: @@
 * AIP Storage
 ** done in one place: src/MCPClient/lib/clientScripts/storeAIP.py
 Ways Archivematica can touch the filesystem:
-* python's open()
+* python's open(), shutil.{move|copy|rm}
-* python's shutil.{move|copy|rm}
+** mostly just in currently processing
 * python's os module (checking if file/directory exists, create directory, remove file)
 * cp, mv, mkdir, rm, chmod as client Scripts
 * dashboard configs (eg. AIP storage location, transfer source)
 ** dashboard.components.main.models.py SourceDirectory, StorageDirectory
 [[Category:Development documentation]]

@@ Line 5: / Line 5: @@
 Goal: Look at all the places Archivematica currently accesses the filesystem, and categorize them.
-Likely Categories:
+Categories:
 * Transfers
-* AIP Storage
+* Quarantine
 * Backlog transfer
-* Processing
+* Currently Processing
 ** touched everywhere, in all the client scripts, with python and client scripts.
 ** Probably best to keep local
-** Already set up to be moved with %sharedDirectory% as long as folder structure inside %sharedDirectory% is preserved
+** Already set up to be move-able with %sharedDirectory% as long as folder structure inside %sharedDirectory% is preserved
 Ways Archivematica can touch the filesystem:
@@ Line 20: / Line 22: @@
 * python's os module (checking if file/directory exists, create directory, remove file)
 * cp, mv, mkdir, rm, chmod as client Scripts
-* dashboard configs (eg. AIP storage location, tranasfer source) javascript
+* dashboard configs (eg. AIP storage location, transfer source)
+*
 [[Category:Development documentation]]

@@ Line 13: / Line 13: @@
 Ways Archivematica can touch the filesystem:
 * python's open()
-* copy/move as client Scripts
+* python's shutil.{move|copy|rm}
 * dashboard configs (eg. AIP storage location, tranasfer source) javascript
+*
 [[Category:Development documentation]]