Difference between revisions of "Requirements"
| Line 24: | Line 24: | ||
* [[Metadata import]] | * [[Metadata import]] | ||
* [[Metrics requirements]] | * [[Metrics requirements]] | ||
| + | * [[Sword API]] | ||
* [[Transfer backlog requirements]] | * [[Transfer backlog requirements]] | ||
* [[Transfer and SIP creation]] | * [[Transfer and SIP creation]] | ||
* [[TRIM exports]] | * [[TRIM exports]] | ||
| + | |||
[[Category:Development documentation]] | [[Category:Development documentation]] | ||
Revision as of 13:38, 27 January 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)
- Manual normalization requirements and testing procedures
- Metadata import
- Metrics requirements
- Sword API
- Transfer backlog requirements
- Transfer and SIP creation
- TRIM exports