Difference between revisions of "UC-1.2.1"
Jump to navigation
Jump to search
(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 1: | Line 1: | ||
| − | + | <span class="pageTitle">Implement an arrangement policy</span> | |
| − | + | [[Main Page]] > [[System requirements]] > [[Use cases]] | |
| − | |||
| + | <span class="useCaseHead">Summary</span> | ||
| − | + | '''Overview''': | |
| + | *An institution establishes its arrangement policy and customizes the application to implement it. | ||
| − | |||
| − | + | '''Context (parent cases)''': | |
| − | + | *[[UC-1|UC-1 Implement a system of control]] | |
| − | |||
| − | |- | + | *[[UC-1.2|UC-1.2 Title]] |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''Actors''' | |
| − | |||
| − | |||
| − | |||
| − | + | *Primary actor: institution. | |
| − | |||
| − | |||
| − | + | *Secondary actors: administrator. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | <span class="useCaseHead">Description</span> | |
| − | |||
| − | |||
| − | + | '''Preconditions''': | |
| − | + | ||
| − | + | *Institution establishes a policy on arrangement. | |
| + | |||
| + | |||
| + | '''Trigger''' | ||
| + | |||
| + | *N/A. | ||
| + | |||
| + | |||
| + | '''Successful outcome''' | ||
| + | |||
| + | *Application customized so that user options reflect institution's arrangement policy.. | ||
| + | |||
| + | |||
| + | '''Main scenario''' | ||
| − | |||
| − | |||
| − | |||
Scenario A: | Scenario A: | ||
| Line 63: | Line 54: | ||
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. | 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: | Scenario B: | ||
| Line 71: | Line 62: | ||
*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 group" but term no longer allowed for new descriptions. | ||
| − | + | 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. | |
| + | |||
| + | |||
| + | <span class="useCaseHead">Requirements</span> | ||
| + | |||
| + | '''Functional requirements''' | ||
| + | |||
| + | *[[FR-1.2.1|FR-1.2.1 Describe material at multiple levels of arrangement]] | ||
| + | |||
| + | *[[FR-1.2.2|FR-1.2.2 Establish the highest level of arrangement]] | ||
| + | |||
| + | *[[FR-1.2.3|FR-1.2.3 Establish the number of levels of arrangement]] | ||
| + | |||
| + | |||
| + | '''Metadata requirements''' | ||
| + | |||
| + | *[[MR-1.1.3|MR-1.1.3 Indicate the level of description]] | ||
| + | |||
| + | |||
| + | '''Technical requirements''' | ||
| + | |||
| + | *N/A | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | <span class="useCaseHead">Documentation</span> | |
| − | + | '''Diagrams''' | |
| − | + | *N/A | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | + | '''User Manual''': | |
| − | |||
| − | |||
| − | | | + | *[[UM-3.5|UM-3 Add / edit content > UM-3.5 Edit taxonomies (terms)]] |
Revision as of 15:07, 11 July 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.
Implement an arrangement policy
Main Page > System requirements > Use cases
Summary
Overview:
- An institution establishes its arrangement policy and customizes the application to implement it.
Context (parent cases):
Actors
- Primary actor: institution.
- Secondary actors: administrator.
Description
Preconditions:
- Institution establishes a policy on arrangement.
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.
- 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.
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.
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.
Requirements
Functional requirements
Metadata requirements
Technical requirements
- N/A
Documentation
Diagrams
- N/A
User Manual: