Difference between revisions of "Options for Repository Software"
From CURATEcamp
Doug Reside (talk | contribs) |
Doug Reside (talk | contribs) (→Tools we are using) |
||
| Line 9: | Line 9: | ||
* Omeka | * Omeka | ||
* E.R.A. | * E.R.A. | ||
| + | |||
| + | == What is a Repository == | ||
| + | |||
| + | Provisional definition: A file system with transactional ingest (let's you know that the file was copied properly) with regular backups and abstracted links to actual file stores managed by a metadata system that may also include other metadata information. | ||
| + | |||
| + | == Microservices needed by repository developers == | ||
| + | |||
| + | * File storage | ||
| + | * Integrity checking | ||
| + | * Metadata linking | ||
| + | * Public access | ||
| + | * Backups | ||
| + | * Transaction based ingest | ||
Revision as of 17:12, 26 July 2012
Tools we are using
- Fedora
- DSpace
- Archivematica
- OpenStack / SWIFT
- LOCKSS
- Ex Libris
- Omeka
- E.R.A.
What is a Repository
Provisional definition: A file system with transactional ingest (let's you know that the file was copied properly) with regular backups and abstracted links to actual file stores managed by a metadata system that may also include other metadata information.
Microservices needed by repository developers
- File storage
- Integrity checking
- Metadata linking
- Public access
- Backups
- Transaction based ingest
