Difference between revisions of "Storage API"
Jump to navigation
Jump to search
(Initial setup, stub) |
(Ways Archivematica can touch the filesystem start) |
||
| Line 10: | Line 10: | ||
* Backlog transfer | * Backlog transfer | ||
* Processing | * Processing | ||
| + | |||
| + | Ways Archivematica can touch the filesystem: | ||
| + | * python's open() | ||
| + | * copy/move as client Scripts | ||
| + | * dashboard configs (eg. AIP storage location, tranasfer source) javascript | ||
| + | * | ||
[[Category:Development documentation]] | [[Category:Development documentation]] | ||
Revision as of 18:48, 3 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
- Backlog transfer
- Processing
Ways Archivematica can touch the filesystem:
- python's open()
- copy/move as client Scripts
- dashboard configs (eg. AIP storage location, tranasfer source) javascript