Difference between revisions of "Storage API"

From Archivematica
Jump to navigation Jump to search
m (More archivematica and filesystem)
(→‎Initial Research: More on how Archivematica touches FS)
Line 6: Line 6:
  
 
Likely Categories:
 
Likely Categories:
* Transfers
+
* Transfers                                                                                                                                                                                    
 
* AIP Storage
 
* AIP Storage
 +
** done in one place: src/MCPClient/lib/clientScripts/storeAIP.py
 
* Backlog transfer
 
* Backlog transfer
 
* Processing
 
* 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
  
 
Ways Archivematica can touch the filesystem:
 
Ways Archivematica can touch the filesystem:
 
* python's open()
 
* python's open()
 
* python's shutil.{move|copy|rm}
 
* python's shutil.{move|copy|rm}
 +
* python's os module (checking if file/directory exists, create directory, remove file)
 
* cp, mv, mkdir, rm, chmod as client Scripts
 
* cp, mv, mkdir, rm, chmod as client Scripts
 
* dashboard configs (eg. AIP storage location, tranasfer source) javascript
 
* dashboard configs (eg. AIP storage location, tranasfer source) javascript
 
*  
 
*  
 +
  
 
[[Category:Development documentation]]
 
[[Category:Development documentation]]

Revision as of 13:15, 4 June 2013

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
    • done in one place: src/MCPClient/lib/clientScripts/storeAIP.py
  • Backlog transfer
  • 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

Ways Archivematica can touch the filesystem:

  • python's open()
  • python's shutil.{move|copy|rm}
  • 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