Difference between revisions of "USC-1.2.1"
(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...) |
|||
(4 intermediate revisions by the same user not shown) | |||
Line 14: | Line 14: | ||
|- valign="top" align="left" | |- valign="top" align="left" | ||
− | | width="100" rowspan=" | + | | width="100" rowspan="3" style="background:silver" | Summary |
! width="150" | ID number | ! width="150" | ID number | ||
− | | width="700" | 1.2.1 | + | | width="700" | USC-1.2.1 |
|- valign="top" align="left" | |- valign="top" align="left" | ||
Line 24: | Line 24: | ||
|- valign="top" align="left" | |- valign="top" align="left" | ||
− | ! | + | ! Actors |
| | | | ||
+ | Primary actor: | ||
*Institution. | *Institution. | ||
− | + | Secondary actor: | |
− | |||
− | |||
*Administrator. | *Administrator. | ||
Line 67: | Line 66: | ||
Scenario B: | Scenario B: | ||
− | Institution changes policy and | + | 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 | + | *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. | *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" | |- valign="top" align="left" | ||
− | | rowspan="3" style="background:silver" | | + | | rowspan="3" style="background:silver" | Associated requirements |
! Functional requirements | ! Functional requirements | ||
| | | | ||
Line 91: | Line 90: | ||
|- valign="top" align="left" | |- valign="top" align="left" | ||
− | + | | style="background:silver" | Diagrams | |
+ | | colspan="2" | | ||
+ | |||
+ | |- valign="top" align="left" | ||
+ | | style="background:silver" | User manual | ||
| colspan="2" | | | colspan="2" | | ||
+ | *[[Add / edit archival descriptions#Identity area | Add / edit content > Archival descriptions > Edit screen (data entry) > Identity area]]: step 1 | ||
|} | |} |
Latest revision as of 18:56, 5 May 2008
Please note that ICA-AtoM is no longer actively supported by Artefactual Systems.
Visit https://www.accesstomemory.org for information about AtoM, the currently supported version.
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 | USC-1.2.1 Implement an arrangement policy
- USC-1.2 Implement a system of intellectual control
Implement an arrangement policy
Implement an arrangement policy | ||
Summary | ID number | USC-1.2.1 |
---|---|---|
Overview |
An institution establishes its arrangement policy and customizes the application to implement it. | |
Actors |
Primary actor:
Secondary actor:
| |
Description | Preconditions |
|
Trigger |
| |
Successful outcome |
| |
Main scenario |
Scenario A: 1. Institution establishes the highest level of arrangement it will employ.
2. Institution establishes the number of levels of arrangement it will employ.
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. | |
Exceptions / variations |
Scenario B: 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.
| |
Associated requirements | Functional requirements | |
Metadata requirements | ||
Technical requirements | ||
Diagrams | ||
User manual |