FNC-1.2.1
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 > Functional requirements > FNC-1 Implement a system of control > FNC-1.2 Implement a system of intellectual control > Describe archival materials at multiple levels of description
Describe archival materials at multiple levels of description
Requirement number | FNC-1.2.1 |
---|---|
Requirement name | Describe archival materials at multiple levels of description |
Context (parent requirements) | |
Requirement specification |
Archivists must be able to describe materials at multiple levels of arrangement.
The application must support multi-level description with inheritance and consistency across levels. |
Source quotation |
ISAD(G) I.8 ISAD(G) Section 1 ISAD(G) Section 2 OSARIS 1.1.1 OSARIS 2.1.1 |
Associated metadata requirements | |
Associated quality requirements |
Provide drop-down lists to select level of description. Provide pick-lists to select parent level of desription / assign position in hierarchy of arrangement. Show inherited information at lower levels of descripiton. Calculate values at higher levels of description from lower (e.g. date ranges). |
Associated technical requirements | |
ICA-AtoM implementation |
ICA-AtoM ships with a default schema for levels of description (fonds, sub-fonds, series, sub-series, file, item). Administrators can edit to reflect institutional policy / terminology. ICA-AtoM imposes no limits on the number of levels that can be used. A unit's position in the hierarchy is determined by the value selected in "Parent level". A description is recognized as the highest level when the "Parent level" field is blank. "Discrete items" (items not linked to a higher parent level) are permitted: simply leave the "Parent level" blank. |
Known issues |
ICA-AtoM (v0.6) does not provide for calculating values at higher levels from lower (e.g. date range); these must be manually entered at each level. The application does not enforce consistency. |
Use cases |
[[USC-1.2.1 | USC-1.2.1 Implement an arrangement policy. |
User Manual sections |
Add / edit content > Archival descriptions > Edit screen (data entry) > Identity area |