Difference between revisions of "USC-1.2.1"
Line 16: | Line 16: | ||
| width="100" rowspan="3" style="background:silver" | Summary | | 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" |
Revision as of 18:13, 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 |