Difference between revisions of "USC-1.2.1"

From ICA-AtoM
Jump to navigation Jump to search
 
Line 14: Line 14:
  
 
|- valign="top" align="left"
 
|- 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="150" | ID number
 
| width="700" | 1.2.1
 
| width="700" | 1.2.1
Line 24: Line 24:
  
 
|- valign="top" align="left"
 
|- valign="top" align="left"
! Primary actor
+
! Actors
 
|  
 
|  
 +
Primary actor:
 
*Institution.
 
*Institution.
  
|- valign="top" align="left"
+
Secondary actor:
! Secondary actor
 
|
 
 
*Administrator.
 
*Administrator.
  

Revision as of 17:40, 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


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.

Actors

Primary actor:

  • Institution.

Secondary actor:

  • Administrator.
Description Preconditions
  • n/a
Trigger
  • n/a
Successful outcome
  • Application customized so that user data-entry interface reflects 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.
  • 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
Metadata requirements
Technical requirements
Diagrams