Difference between revisions of "Requirements"
| Line 21: | Line 21: | ||
* [[Format identification requirements]] | * [[Format identification requirements]] | ||
* [[Format policy registry requirements|Format Policy Registry (FPR)]] | * [[Format policy registry requirements|Format Policy Registry (FPR)]] | ||
| + | * [[LOCKSS_Integration|LOCKSS integration]] | ||
* [[Manual normalization requirements and testing procedures]] | * [[Manual normalization requirements and testing procedures]] | ||
* [[Metadata import]] | * [[Metadata import]] | ||
Revision as of 11:35, 14 March 2014
Main Page > Documentation > Requirements
The Archivematica UML Activity Diagrams are the baseline requirements for the system's default micro-services workflow. These were derived from an in-depth analysis of the ISO-OAIS functions which led to a series of OAIS Use Cases and OAIS Activity Diagrams.
Each Archivematica software release builds on the OAIS use cases and implements a growing set of format policies. These are based on an analysis of open standards, open source normalization tools and the significant characteristics of specific media types.
End-user requirements are derived from Archivematica pilot implementation projects and the project's discussion list. They are documented in the development roadmap and issues list.
Requirements pages
- Advanced AIP index search
- AIP re-ingest
- Archivists Toolkit integration
- Configuration settings dashboard UI
- Database Data Management
- Dataset preservation
- Digital forensics image ingest
- DSpace integration
- Processing_report
- File Browser Requirements
- Format identification requirements
- Format Policy Registry (FPR)
- LOCKSS integration
- Manual normalization requirements and testing procedures
- Metadata import
- Metrics requirements
- Sword API
- Transfer backlog requirements
- Transfer and SIP creation
- TRIM exports