Difference between revisions of "Requirements"

From Archivematica
Jump to navigation Jump to search
 
(49 intermediate revisions by 6 users not shown)
Line 1: Line 1:
−
[[Main Page]] > Requirements
+
[[Main Page]] > [[Documentation]] > Requirements
  
  
−
The Archivematica [[UML Activity Diagrams]] are the baseline requirements for the current release.
+
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]].
  
−
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 [[format policies]]. These are based on an analysis of open standards, open source normalization tools and the [[significant characteristics]] of specific media types.
  
−
Each Archivematica release is supported with [[documentation]] that provides instructions on how to use the virtual appliance to meet the baseline system requirements.
+
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].
  
−
Additional requirements, requirement formats, and requirement sources will be added over successive system iterations.
+
''Requirements pages''
 +
* [[Advanced AIP index search]]
 +
* [[AIP re-ingest]]
 +
* [[Appraisal Arrangement tab]]
 +
* [[Archivists Toolkit integration]]
 +
* [[ArchivesSpace integration]]
 +
* [[Configuration settings#UI_mockup_for_configuration_settings| Configuration settings dashboard UI]]
 +
* [[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]]
  
  
−
==Media type preservation requirements==
 
  
−
Normalization is one preservation strategy that can be implemented using Archivematica.
+
[[Category:Development documentation]]
−
 
 
−
Archivematica uses the National Archives of Australia's Xena software to convert certain file formats to xml-based formats on ingest. A full list of the file types Xena can normalize is available at [http://xena.sourceforge.net/help.php?page=normformats.html http://xena.sourceforge.net/help.php?page=normformats.html].
 
−
 
 
−
However, some types of objects cannot be normalized by Xena. Also, it may be desirable to adopt other preservation plans for certain types of objects based on institutional requirements and preferences.
 
−
 
 
−
For further details on preservation planning in Archivematica see [[Media type preservation plans]].
 

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

Retrieved from "https://wiki.archivematica.org/index.php?title=Requirements&oldid=11349"