Difference between revisions of "Requirements"
m |
|||
| Line 19: | Line 19: | ||
* [[Dataverse]] | * [[Dataverse]] | ||
* [[Digital forensics image ingest]] | * [[Digital forensics image ingest]] | ||
| + | * [[DIP storage to designated location]] | ||
* [[Directory printer for recording original order]] | * [[Directory printer for recording original order]] | ||
| − | |||
* [[DSpace integration]] | * [[DSpace integration]] | ||
* [[OCR text in DIP]] | * [[OCR text in DIP]] | ||
| Line 33: | Line 33: | ||
* [[Metadata import]] | * [[Metadata import]] | ||
* [[Metrics requirements]] | * [[Metrics requirements]] | ||
| + | * [[Object-level PREMIS rights import]] | ||
* [[Sword API]] | * [[Sword API]] | ||
* [[Transfer backlog requirements]] | * [[Transfer backlog requirements]] | ||
Latest revision as of 12:13, 6 July 2016
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
- Appraisal Arrangement tab
- Archivists Toolkit integration
- ArchivesSpace integration
- Configuration settings dashboard UI
- Database Data Management
- Dataset preservation
- Dataverse
- Digital forensics image ingest
- DIP storage to designated location
- Directory printer for recording original order
- DSpace integration
- OCR text in DIP
- Processing_report
- File Browser Requirements
- Fixity checking and reporting
- Format identification requirements
- Format Policy Registry (FPR)
- LOCKSS integration
- Manual normalization requirements and testing procedures
- MediaConch integration
- Metadata import
- Metrics requirements
- Object-level PREMIS rights import
- Sword API
- Transfer backlog requirements
- Transfer and SIP creation
- TRIM exports