Difference between revisions of "Release 0.5 Documentation"

From Archivematica
Jump to navigation Jump to search
Line 3: Line 3:
  
  
'''PLEASE NOTE''': detailed Release 0.5 documentation will be added shortly. In the meanwhile, the following workflow diagram illustrates the steps required to ingest, store and provide access to digital objects in Archivematica 0.5:
+
The following workflow diagram illustrates the steps required to ingest, store and provide access to digital objects in Archivematica 0.5:
 
*Archivematica 0.5 workflow: ([[:File:Archivematica_workflow_05.pdf|PDF]]) ([[:File:Archivematica_workflow_05.odg|OpenDocument]]).
 
*Archivematica 0.5 workflow: ([[:File:Archivematica_workflow_05.pdf|PDF]]) ([[:File:Archivematica_workflow_05.odg|OpenDocument]]).
  
Line 10: Line 10:
 
----
 
----
  
The system documentation for release 0.5 corresponds directly to each numbered activity in the Archivematica [[UML Activity Diagrams]]. The documentation provides instructions on how these activities might be carried out using the current Archivematica release.  
+
The user documentation for release 0.5 corresponds directly to each activity in the workflow diagram provided above. Where possible, each step is also linked back to the relevant numbered activity in the Archivematica [[UML Activity Diagrams]] and [[OAIS Use Cases]]. The documentation provides instructions on how these activities can be carried out using the current Archivematica release.  
  
 
Wherever possible, these activities are assigned to software or technical tools. If it is not possible to automate these functions in the current system iteration, the functions are incorporated into a manual procedure to be carried out by the end user. This ensures that the entire set of requirements are being carried out in the system, which is an integrated whole of software, people and procedures. The goal is to add more detailed requirements along with increasing integration and functionality of the software components with each system iteration.
 
Wherever possible, these activities are assigned to software or technical tools. If it is not possible to automate these functions in the current system iteration, the functions are incorporated into a manual procedure to be carried out by the end user. This ensures that the entire set of requirements are being carried out in the system, which is an integrated whole of software, people and procedures. The goal is to add more detailed requirements along with increasing integration and functionality of the software components with each system iteration.

Revision as of 18:44, 19 November 2009

Main Page > Documentation > Release 0.5 Documentation


The following workflow diagram illustrates the steps required to ingest, store and provide access to digital objects in Archivematica 0.5:



The user documentation for release 0.5 corresponds directly to each activity in the workflow diagram provided above. Where possible, each step is also linked back to the relevant numbered activity in the Archivematica UML Activity Diagrams and OAIS Use Cases. The documentation provides instructions on how these activities can be carried out using the current Archivematica release.

Wherever possible, these activities are assigned to software or technical tools. If it is not possible to automate these functions in the current system iteration, the functions are incorporated into a manual procedure to be carried out by the end user. This ensures that the entire set of requirements are being carried out in the system, which is an integrated whole of software, people and procedures. The goal is to add more detailed requirements along with increasing integration and functionality of the software components with each system iteration.