Release 0.3 Documentation - Revision history

Peter at 22:40, 25 September 2009

2009-09-25T22:40:41Z

Evelyn McLellan at 22:59, 4 September 2009

2009-09-04T22:59:27Z

Evelyn McLellan at 20:49, 4 September 2009

2009-09-04T20:49:13Z

Evelyn McLellan at 20:47, 4 September 2009

2009-09-04T20:47:29Z

Evelyn McLellan at 20:44, 4 September 2009

2009-09-04T20:44:39Z

Peter at 22:45, 3 September 2009

2009-09-03T22:45:38Z

Peter at 22:44, 3 September 2009

2009-09-03T22:44:49Z

Peter: Created page with ' The system documentation for release 0.3 corresponds directly to each numbered activity in the Archivematica UML Activity Diagrams. The documentation provides instructions o…'

2009-09-03T22:44:19Z

Created page with ' The system documentation for release 0.3 corresponds directly to each numbered activity in the Archivematica UML Activity Diagrams. The documentation provides instructions o…'

New page

The system documentation for release 0.3 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.

← Older revision		Revision as of 22:40, 25 September 2009
Line 10:		Line 10:
	*[[Access (0.3)]]		*[[Access (0.3)]]
	*[[Administration (0.3)]]		*[[Administration (0.3)]]
		+
		+	NOTE: For instructions on how to use individual tools in Archivematica, see [[Using Archivematica Tools]].

← Older revision		Revision as of 22:59, 4 September 2009
Line 1:		Line 1:
−	[[Main Page]] > [[Documentation]] > Release 0.3	+	[[Main Page]] > [[Documentation]] > Release 0.3 Documentation

	The system documentation for release 0.3 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 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.

@@ Line 6: / Line 6: @@
 *[[Ingest (0.3)]]
-*[[0.3 Archival Storage]]
+*[[Archival Storage (0.3)]]
-*[[0.3 Data Management]]
+*[[Data Management (0.3)]]
-*[[0.3 Access]]
+*[[Access (0.3)]]
-*[[0.3 Administration]]
+*[[Administration (0.3)]]

@@ Line 5: / Line 5: @@
 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.
-*[[0.3 Ingest]]
+*[[Ingest (0.3)]]
 *[[0.3 Archival Storage]]
 *[[0.3 Data Management]]
 *[[0.3 Access]]
 *[[0.3 Administration]]

← Older revision		Revision as of 20:44, 4 September 2009
Line 4:		Line 4:

	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.
		+
		+	*[[0.3 Ingest]]
		+	*[[0.3 Archival Storage]]
		+	*[[0.3 Data Management]]
		+	*[[0.3 Access]]
		+	*[[0.3 Administration]]

← Older revision		Revision as of 22:45, 3 September 2009
Line 3:		Line 3:
	The system documentation for release 0.3 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 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.	+	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.

← Older revision		Revision as of 22:44, 3 September 2009
Line 1:		Line 1:
		+	[[Main Page]] > [[Documentation]] > Release 0.3

	The system documentation for release 0.3 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 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.		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.