Difference between revisions of "FNC-1.2.1"
| Line 1: | Line 1: | ||
| − | + | <span class="pageTitle">Describe archival materials at multiple levels of description</span> | |
| − | + | [[Main Page]] > [[System Requirements]] > [[Functional requirements]] | |
| − | |||
| − | |||
| − | + | '''Specification''' | |
| − | |||
| − | |||
| − | + | Archivists must be able to describe materials at multiple [[Level of descripiton|levels]], reflecting the levels of arrangement. | |
| − | |||
| − | |||
| − | + | *Descriptions at lower [[Level of description|levels]] should inherit information from higher [[Level of description|levels]] (e.g. [[Creator|creator]]). | |
| − | |||
| − | |||
| − | |||
| − | *Descriptions at lower levels should inherit information from higher levels (e.g. creator | ||
| − | |||
| − | + | *Descriptions at higher [[Level of description|levels]] should be consistent with information at lower [[Level of description|levels]] (e.g. dates and extent). | |
| − | + | The application must support multi-level description with inheritance and consistency across [[Level of description|levels]]. | |
| − | |||
| − | |||
| − | [[ | ||
| − | |||
| − | + | '''Context (parent requirements)''' | |
| − | |||
| − | |||
| − | |||
| − | [[ | + | *[[FNC-1|FNC-1 Establish a system of control]] |
| − | [[ | + | *[[FNC-1.2|FNC-1.2 Establish systems of intellectual control]] |
| − | |||
| − | + | '''Source quotation''' | |
| − | |- | + | *[[RS-1#i.8|ISAD(G) I.8]] |
| − | | | + | |
| − | + | [[RS-1#1|ISAD(G) Section 1]] | |
| + | |||
| + | [[RS-1#2|ISAD(G) Section 2]] | ||
| + | |||
| + | [[RS-4#1.1.1|OSARIS 1.1.1]] | ||
| + | |||
| + | [[RS-4#2.1.1|OSARIS 2.1.1]] | ||
| + | |||
| + | |||
| + | '''Associated metadata requirements''' | ||
| + | |||
[[MTD-1.1.3 | MTD-1.1.3 Indicate the level of descripiton]] | [[MTD-1.1.3 | MTD-1.1.3 Indicate the level of descripiton]] | ||
Revision as of 18:12, 6 June 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.
Describe archival materials at multiple levels of description
Main Page > System Requirements > Functional requirements
Specification
Archivists must be able to describe materials at multiple levels, reflecting the levels of arrangement.
- Descriptions at higher levels should be consistent with information at lower levels (e.g. dates and extent).
The application must support multi-level description with inheritance and consistency across levels.
Context (parent requirements)
Source quotation
Associated metadata requirements
MTD-1.1.3 Indicate the level of descripiton
|- valign="top" align="left" | style="background:silver" | 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).
|- valign="top" align="left" | style="background:silver" | Associated technical requirements |
|- valign="top" align="left" | style="background:silver" | 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 the Parent level field.
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.
|- valign="top" align="left" | style="background:silver" | Known issues | ICA-AtoM (v0.6) cannot currently calculate values at higher levels from lower (e.g. date range); these must be manually entered at each level. The application does not enforce consistency.
|- valign="top" align="left" | style="background:silver" | Use cases | USC-1.2.1 Implement an arrangement policy
|- valign="top" align="left" | style="background:silver" | User Manual sections | Add / edit content > Archival descriptions > Edit screen (data entry) > Identity area
|}