UC-1.2.1 - Revision history

Richard at 21:12, 11 July 2008

2008-07-11T21:12:38Z

Richard at 21:11, 11 July 2008

2008-07-11T21:11:51Z

Richard at 21:09, 11 July 2008

2008-07-11T21:09:30Z

Richard at 21:07, 11 July 2008

2008-07-11T21:07:44Z

Richard: New page: Main Page > System Requirements > Use cases > USC-1 Establish a system of control == Establish a system of control == These use cases relate to implementing policy decisions ...

2008-07-11T19:04:43Z

New page: Main Page > System Requirements > Use cases > USC-1 Establish a system of control == Establish a system of control == These use cases relate to implementing policy decisions ...

New page

[[Main Page]] > [[System Requirements]] > [[Use cases]] > USC-1 Establish a system of control

== Establish a system of control ==

These use cases relate to implementing policy decisions in the application.

=== Define system scope ===

=== Establish a system of intellectual control ===

==== Implement an arrangement policy ====

<span id="USC-1.2.1"></span>
{| border="1" cellpadding="2"

|- valign="top" align="left" style="background:#00008B; color:white"
| colspan="3" | Implement an arrangement policy

|- valign="top" align="left"
| width="100" rowspan="4" style="background:silver" | Summary
! width="150" | ID number
| width="700" | 1.2.1

|- valign="top" align="left"
! Overview
|
An institution establishes its arrangement policy and customizes the application to implement it.

|- valign="top" align="left"
! Primary actor
| Institution.

|- valign="top" align="left"
! Secondary actor
| Administrator.

|- valign="top" align="left"
| rowspan="5" style="background:silver" | Description
! Preconditions
| n/a

|- valign="top" align="left"
! Trigger
| n/a

|- valign="top" align="left"
! Successful outcome
| Application customized so that user options reflect institution's arrangement policy.

|- valign="top" align="left"
! Main scenario
|
Scenario A:

1. Institution establishes the highest level of arrangement it will employ.
*E.g. Fonds, series, record group established as highest level.

2. Institution establishes the number of levels of arrangement it will employ.
*E.g. no sub-fonds, no more than three series levels (series, sub- and sub-sub-series).

3. Administrator edits the default "Levels of description" taxonomy shipped with ICA-AtoM, so that drop-down lists show only levels and terms allowed by policy.

|- valign="top" align="left"
! Exceptions / variations
|
Scenario B:

Institution changes policy and for a transitional period retains old data values in the application (pending conversion) but allows users to use only new values.
*E.g. application contains descriptions registered as "Record group" but term no longer allowed for new descriptions.

As of version 0.6, ICA-AtoM cannot accommodate this scenario. A term cannot be deleted from a taxonomy if other records are already registered to it. In a future release, it will be possible to make taxonomy terms "inactive" so that data integrity is protected, while drop-down list for on-going data entry show only the preferred terms.

|- valign="top" align="left"
| rowspan="3" style="background:silver" | Requirements
! Functional requirements
|
[[FNC-1 Establish a system of control#FNC-1.2.1 | FNC-1.2.1 Describe material at multiple levels of arrangement]]

[[FNC-1 Establish a system of control#FNC-1.2.2 | FNC-1.2.2 Establish the highest level of arrangement]]

[[FNC-1 Establish a system of control#FNC-1.2.3 | FNC-1.2.3 Establish the number of levels of arrangement]]

|- valign="top" align="left"
! Metadata requirements
|
[[MTD1 Record information about archival materials#MTD1.1.3 | MTD-1.1.3 Indication the level of description]]

|- valign="top" align="left"
! Technical requirements
|

|- valign="top" align="left"
! style="background:silver" | Diagrams
| colspan="2" |

|}

@@ Line 6: / Line 6: @@
 == Summary ==
-'''Overview''':
+'''Overview'''
 *An institution establishes its arrangement policy and customizes the application to implement it.
-'''Context (parent cases)''':
+'''Context (parent cases)'''
 *[[UC-1|UC-1 Implement a system of control]]
@@ Line 27: / Line 27: @@
 == Description ==
-'''Preconditions''':
+'''Preconditions'''
 *Institution establishes a policy on arrangement.
@@ Line 55: / Line 55: @@
-'''Exceptions / variations''':
+'''Exceptions / variations'''
 Scenario B:
@@ Line 93: / Line 93: @@
-'''User Manual''':
+'''User Manual'''
 *[[UM-3.5|UM-3 Add / edit content > UM-3.5 Edit taxonomies (terms)]]

← Older revision		Revision as of 21:11, 11 July 2008
Line 1:		Line 1:
		+	__NOTOC__
	<span class="pageTitle">Implement an arrangement policy</span>		<span class="pageTitle">Implement an arrangement policy</span>

@@ Line 3: / Line 3: @@
 [[Main Page]] > [[System requirements]] > [[Use cases]]
+== Summary ==
 '''Overview''':
@@ Line 25: / Line 24: @@
-<span class="useCaseHead">Description</span>
+== Description ==
 '''Preconditions''':
@@ Line 65: / Line 64: @@
-<span class="useCaseHead">Requirements</span>
+== Requirements ==
 '''Functional requirements'''
@@ Line 86: / Line 85: @@
-<span class="useCaseHead">Documentation</span>
+== Documentation ==
 '''Diagrams'''

@@ Line 1: / Line 1: @@
-[[Main Page]] > [[System Requirements]] > [[Use cases]] > USC-1 Establish a system of control
+<span class="pageTitle">Implement an arrangement policy</span>
-== Establish a system of control ==
+[[Main Page]] > [[System requirements]] > [[Use cases]]
-=== Define system scope ===
+'''Overview''':
-==== Implement an arrangement policy ====
+'''Context (parent cases)''':
-<span id="USC-1.2.1"></span>
+*[[UC-1|UC-1 Implement a system of control]]
-|- valign="top" align="left" style="background:#00008B; color:white"
+*[[UC-1.2|UC-1.2 Title]]
-|- valign="top" align="left"
+'''Actors'''
-|- valign="top" align="left"
+*Primary actor: institution.
-|- valign="top" align="left"
+*Secondary actors: administrator.
-|- valign="top" align="left"
+<span class="useCaseHead">Description</span>
-|- valign="top" align="left"
+'''Preconditions''':
-! Successful outcome
-| Application customized so that user options reflect institution's arrangement policy.
+*Institution establishes a policy on arrangement.
 Scenario A:
@@ Line 63: / Line 54: @@
 . Administrator edits the default "Levels of description" taxonomy shipped with ICA-AtoM, so that drop-down lists show only levels and terms allowed by policy.
-|- valign="top" align="left"
-! Exceptions / variations
+'''Exceptions / variations''':
-−
 Scenario B:
@@ Line 71: / Line 62: @@
 *E.g. application contains descriptions registered as "Record group" but term no longer allowed for new descriptions.
-As of version 0.6, ICA-AtoM cannot accommodate this scenario. A term cannot be deleted from a taxonomy if other records are already registered to it. In a future release, it will be possible to make taxonomy terms "inactive" so that data integrity is protected, while drop-down list for on-going data entry show only the preferred terms.
+ICA-AtoM cannot currently (v1.0 beta) accommodate this scenario. A term cannot be deleted from a taxonomy if other records are already registered to it. In a future release, it will be possible to make taxonomy terms "inactive" so that data integrity is protected, while drop-down list for on-going data entry show only the preferred terms.
-[[FNC-1 Establish a system of control#FNC-1.2.2 | FNC-1.2.2	Establish the highest level of arrangement]]
+<span class="useCaseHead">Documentation</span>
-[[FNC-1 Establish a system of control#FNC-1.2.3 | FNC-1.2.3	Establish the number of levels of arrangement]]
+'''Diagrams'''
-|- valign="top" align="left"
+*N/A
-|- valign="top" align="left"
+'''User Manual''':
-|}
+*[[UM-3.5|UM-3 Add / edit content > UM-3.5 Edit taxonomies (terms)]]