Difference between revisions of "Requirements"
| Line 14: | Line 14: | ||
* [[Database Data Management]] | * [[Database Data Management]] | ||
* [[DSpace integration]] | * [[DSpace integration]] | ||
| + | * [[Failure report requirements]] | ||
* [[File Browser Requirements]] | * [[File Browser Requirements]] | ||
* [[Format identification requirements]] | * [[Format identification requirements]] | ||
Revision as of 17:27, 31 October 2012
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 media type preservation plans. 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
- Archivists Toolkit integration
- CONTENTdm integration
- Database Data Management
- DSpace integration
- Failure report requirements
- File Browser Requirements
- Format identification requirements
- Format Policy Registry (FPR)
- Metadata import
- Transfer backlog requirements
- Transfer and SIP creation
- TRIM exports