Difference between revisions of "USC-1 Establish a system of control"
(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 ...) |
|||
Line 48: | Line 48: | ||
|- valign="top" align="left" | |- valign="top" align="left" | ||
! Successful outcome | ! Successful outcome | ||
− | | Application customized so that institution's policy | + | | Application customized so that user options reflect institution's arrangement policy. |
|- valign="top" align="left" | |- valign="top" align="left" | ||
Line 78: | Line 78: | ||
| | | | ||
[[FNC-1.2 Establish a system of intellectual control#FNC-1.2.1 | FNC-1.2.1 Describe material at multiple levels of arrangement]] | [[FNC-1.2 Establish a system of intellectual control#FNC-1.2.1 | FNC-1.2.1 Describe material at multiple levels of arrangement]] | ||
+ | |||
[[FNC-1.2 Establish a system of intellectual control#FNC-1.2.2 | FNC-1.2.2 Establish the highest level of arrangement]] | [[FNC-1.2 Establish a system of intellectual control#FNC-1.2.2 | FNC-1.2.2 Establish the highest level of arrangement]] | ||
+ | |||
[[FNC-1.2 Establish a system of intellectual control#FNC-1.2.3 | FNC-1.2.3 Establish the number of levels of arrangement]] | [[FNC-1.2 Establish a system of intellectual control#FNC-1.2.3 | FNC-1.2.3 Establish the number of levels of arrangement]] | ||
Revision as of 17:44, 30 April 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 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
Implement an arrangement policy | ||
Summary | ID number | 1.2.1 |
---|---|---|
Overview |
An institution establishes its arrangement policy and customizes the application to implement it. | |
Primary actor | Institution. | |
Secondary actor | Administrator. | |
Description | Preconditions | n/a |
Trigger | n/a | |
Successful outcome | Application customized so that user options reflect institution's arrangement policy. | |
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 policy and for a transitional period retains old data values in the application (pending conversion) but allows users to use only new values.
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. | |
Requirements | Functional requirements |
FNC-1.2.1 Describe material at multiple levels of arrangement |
Metadata requirements | ||
Technical requirements | ||
Diagrams |