Difference between revisions of "Release 0.3.5 Documentation"
(Created page with 'Main Page > Documentation > Release 0.3.5 Documentation The system documentation for release 0.3.5 corresponds directly to each numbered activity in the Archivematica [[…') |
|||
| Line 1: | Line 1: | ||
[[Main Page]] > [[Documentation]] > Release 0.3.5 Documentation | [[Main Page]] > [[Documentation]] > Release 0.3.5 Documentation | ||
| + | |||
| + | This page is currently under development. For a workflow diagram illustrating the steps required to ingest, store and provide access to digital objects in Archivematica 0.3.5, see ([[:File:Archivematica_workflow.pdf|Archivematica_workflow (PDF version)]]) or ([[:File:Archivematica_workflow.odg|Archivematica_workflow (OpenDocument version)]]). | ||
The system documentation for release 0.3.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 system documentation for release 0.3.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. | ||
Revision as of 16:52, 25 September 2009
Main Page > Documentation > Release 0.3.5 Documentation
This page is currently under development. For a workflow diagram illustrating the steps required to ingest, store and provide access to digital objects in Archivematica 0.3.5, see (Archivematica_workflow (PDF version)) or (Archivematica_workflow (OpenDocument version)).
The system documentation for release 0.3.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.
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.