Difference between revisions of "Requirements"
| Line 11: | Line 11: | ||
| − | ==Format-specific preservation | + | ==Format-specific preservation requirements== |
Normalization is one preservation strategy that can be implemented using Archivematica. | Normalization is one preservation strategy that can be implemented using Archivematica. | ||
Revision as of 11:12, 23 January 2010
Main Page > Requirements
The Archivematica UML Activity Diagrams are the baseline requirements for the current release.
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 release is supported with documentation that provides instructions on how to use the virtual appliance to meet the baseline system requirements.
Additional requirements, requirement formats, and requirement sources will be added over successive system iterations.
Format-specific preservation requirements
Normalization is one preservation strategy that can be implemented using Archivematica.
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.
However, some formats cannot be normalized by Xena. Also, it may be desirable to adopt format-specific preservation plans for certain types of files based on institutional requirements and preferences.
For further discussion of format specific preservation requirements see Format-specific preservation plans.