Difference between revisions of "Requirements"
| Line 8: | Line 8: | ||
End-user requirements are derived from Archivematica pilot implementation projects and the project's [http://groups.google.com/group/archivematica discussion list]. They are documented in the [[development roadmap]] and [http://code.google.com/p/archivematica/issues/list issues list]. | End-user requirements are derived from Archivematica pilot implementation projects and the project's [http://groups.google.com/group/archivematica discussion list]. They are documented in the [[development roadmap]] and [http://code.google.com/p/archivematica/issues/list issues list]. | ||
| − | + | ''Requirements pages'' | |
* [[Advanced AIP index search]] | * [[Advanced AIP index search]] | ||
* [[Archivists Toolkit integration]] | * [[Archivists Toolkit integration]] | ||
Revision as of 17:20, 5 February 2013
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
- Archivists Toolkit integration
- Configuration settings dashboard UI
- CONTENTdm integration
- Database Data Management
- DSpace integration
- Processing_report
- File Browser Requirements
- Format identification requirements
- Format Policy Registry (FPR)
- Metadata import
- Metrics requirements
- Transfer backlog requirements
- Transfer and SIP creation
- TRIM exports