Difference between revisions of "Storage API"
Jump to navigation
Jump to search
(Ways Archivematica can touch the filesystem start) |
m (More archivematica and filesystem) |
||
| Line 13: | Line 13: | ||
Ways Archivematica can touch the filesystem: | Ways Archivematica can touch the filesystem: | ||
* python's open() | * python's open() | ||
| − | * copy | + | * python's shutil.{move|copy|rm} |
| + | * 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 18:56, 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()
- python's shutil.{move|copy|rm}
- cp, mv, mkdir, rm, chmod as client Scripts
- dashboard configs (eg. AIP storage location, tranasfer source) javascript