USC-1.2.1 - Revision history

Richard at 00:56, 6 May 2008

2008-05-06T00:56:51Z

Richard at 00:13, 6 May 2008

2008-05-06T00:13:29Z

Richard at 23:45, 5 May 2008

2008-05-05T23:45:54Z

Richard at 23:42, 5 May 2008

2008-05-05T23:42:39Z

Richard at 23:40, 5 May 2008

2008-05-05T23:40:14Z

Richard: New page: Main Page > System Requirements > Use cases * USC-1 Implement a system of control USC-1.2 Implement a system of intellectual control *USC-1.2.1 | U...

2008-05-05T23:38:41Z

New page: Main Page > System Requirements > Use cases * USC-1 Implement a system of control ** USC-1.2 Implement a system of intellectual control ***USC-1.2.1 | U...

New page

[[Main Page]] > [[System Requirements]] > [[Use cases]]
*[[USC-1 | USC-1 Implement a system of control]]
**[[USC-1.2 | USC-1.2 Implement a system of intellectual control]]
***USC-1.2.1 | USC-1.2.1 Implement an arrangement policy

== 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 data-entry interface reflects 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.2.1 | FNC-1.2.1 Describe material at multiple levels of arrangement]]
*[[FNC-1.2.2 | FNC-1.2.2 Establish the highest level of arrangement]]
*[[FNC-1.2.3 | FNC-1.2.3 Establish the number of levels of arrangement]]

|- valign="top" align="left"
! Metadata requirements
|
*[[MTD-1.1.3 | MTD-1.1.3 Indicate the level of description]]

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

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

|}

@@ Line 92: / Line 92: @@
 | style="background:silver" | Diagrams
 | colspan="2" |
 |}

@@ Line 16: / Line 16: @@
 | width="100" rowspan="3" style="background:silver" | Summary
 ! width="150" | ID number
-| width="700" | 1.2.1
+| width="700" | USC-1.2.1
 |- valign="top" align="left"

@@ Line 66: / Line 66: @@
 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.
+Institution changes its arrangement policy and requires a transitional period in which the application retains old data values (pending conversion) but users are only allowed to use new values.
-*E.g. application contains descriptions registered as "Record group" but term no longer allowed for new descriptions.
+*E.g. application contains descriptions registered as "Record groups" but this term is 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.
@@ Line 90: / Line 90: @@
 |- valign="top" align="left"
-! style="background:silver" | Diagrams
+| style="background:silver" | Diagrams
 | colspan="2" |
 |}

@@ Line 73: / Line 73: @@
 |- valign="top" align="left"
-| rowspan="3" style="background:silver" | Requirements
+| rowspan="3" style="background:silver" | Associated requirements
 ! Functional requirements
+|

@@ Line 14: / Line 14: @@
 |- valign="top" align="left"
-| width="100" rowspan="4" style="background:silver" | Summary
+| width="100" rowspan="3" style="background:silver" | Summary
 ! width="150" | ID number
 | width="700" | 1.2.1
@@ Line 24: / Line 24: @@
 |- valign="top" align="left"
-! Primary actor
+! Actors
+|
 *Institution.
-|- valign="top" align="left"
+Secondary actor:
 *Administrator.