Difference between revisions of "Requirements"

From Archivematica
Jump to navigation Jump to search
 
(33 intermediate revisions by 4 users not shown)
Line 4: Line 4:
 
The Archivematica [[UML Activity Diagrams]] are the baseline requirements for the system's default [[Micro-services|micro-services]] workflow. These were derived from an in-depth analysis of the [http://en.wikipedia.org/wiki/OAIS ISO-OAIS] functions which led to a series of [[OAIS Use Cases]] and [[OAIS Activity Diagrams]].
 
The Archivematica [[UML Activity Diagrams]] are the baseline requirements for the system's default [[Micro-services|micro-services]] workflow. These were derived from an in-depth analysis of the [http://en.wikipedia.org/wiki/OAIS 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.
+
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 [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:_Archivematica|development roadmap]] and [http://code.google.com/p/archivematica/issues/list issues list].
  
--Requirements pages--
+
''Requirements pages''
* [[CONTENTdm_integration]]
+
* [[Advanced AIP index search]]
* [[File_identification_requirements]]
+
* [[AIP re-ingest]]
* [[Format_policy_registry_requirements|Format Policy Registry (FPR)]]
+
* [[Appraisal Arrangement tab]]
* [[File_Browser_Requirements]]
+
* [[Archivists Toolkit integration]]
* [[Archivists_Toolkit_integration]]
+
* [[ArchivesSpace integration]]
* [[Transfer_Backup_Requirements]]
+
* [[Configuration settings#UI_mockup_for_configuration_settings| Configuration settings dashboard UI]]
* [[Transfer_and_SIP_creation]]
+
* [[Database Data Management]]
 +
* [[Dataset_preservation|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 requirements|Format Policy Registry (FPR)]]
 +
* [[LOCKSS_Integration|LOCKSS integration]]
 +
* [[Manual normalization requirements and testing procedures]]
 +
* [[Requirements/MediaConch integration|MediaConch integration]]
 +
* [[Metadata import]]
 +
* [[Metrics requirements]]
 +
* [[Object-level PREMIS rights import]]
 +
* [[Sword API]]
 +
* [[Transfer backlog requirements]]
 +
* [[Transfer and SIP creation]]
 +
* [[TRIM exports]]
 +
 
 +
 
 +
 
 +
[[Category:Development documentation]]

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