Difference between revisions of "FNC-1.2.1"
(New page: Main Page > System Requirements > Functional requirements > FNC-1 Implement a system of control > FNC-1.2 Implement a system of intellectual control >...) |
|||
Line 1: | Line 1: | ||
− | [[Main Page]] > [[System Requirements]] > [[Functional requirements]] > [[FNC-1 | FNC-1 Implement a system of control]] > [[FNC-1.2 | FNC-1.2 Implement a system of intellectual control]] > Describe archival materials at multiple levels of description | + | [[Main Page]] > [[System Requirements]] > [[Functional requirements]] > [[FNC-1 | FNC-1 Implement a system of control]] > [[FNC-1.2 | FNC-1.2 Implement a system of intellectual control]] > FNC-1.2.1 Describe archival materials at multiple levels of description |
== Describe archival materials at multiple levels of description == | == Describe archival materials at multiple levels of description == | ||
Line 13: | Line 13: | ||
| style="background:silver" | Requirement name | | style="background:silver" | Requirement name | ||
| Describe archival materials at multiple levels of description | | Describe archival materials at multiple levels of description | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- valign="top" align="left" | |- valign="top" align="left" | ||
Line 29: | Line 22: | ||
The application must support multi-level description with inheritance and consistency across levels. | The application must support multi-level description with inheritance and consistency across levels. | ||
+ | |||
+ | |- valign="top" align="left" | ||
+ | | style="background:silver" | Context (parent requirements) | ||
+ | | | ||
+ | [[FNC-1 | FNC-1 Establish a system of control]] | ||
+ | |||
+ | [[FNC-1.2 | FNC-1.2 Establish systems of intellectual control]] | ||
|- valign="top" align="left" | |- valign="top" align="left" | ||
Line 34: | Line 34: | ||
| | | | ||
[[ISAD(G)#isadi8 | ISAD(G) I.8 ]] | [[ISAD(G)#isadi8 | ISAD(G) I.8 ]] | ||
+ | |||
[[ISAD(G)#isad1 | ISAD(G) Section 1 ]] | [[ISAD(G)#isad1 | ISAD(G) Section 1 ]] | ||
+ | |||
[[ISAD(G)#isad2 | ISAD(G) Section 2 ]] | [[ISAD(G)#isad2 | ISAD(G) Section 2 ]] | ||
+ | |||
[[OSARIS#osaris1.1.1 | OSARIS 1.1.1]] | [[OSARIS#osaris1.1.1 | OSARIS 1.1.1]] | ||
+ | |||
[[OSARIS#osaris2.1.1 | OSARIS 2.1.1]] | [[OSARIS#osaris2.1.1 | OSARIS 2.1.1]] | ||
Line 64: | Line 68: | ||
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 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 " | + | 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 <span class="field">ParentLevel</span> field. |
+ | |||
+ | A description is recognized as the highest level when the <span class="field">ParentLevel</span> field is blank. | ||
− | + | "Discrete items" (items not linked to a higher parent level) are permitted: simply leave the <span class="field">ParentLevel</span> blank. | |
|- valign="top" align="left" | |- valign="top" align="left" | ||
| style="background:silver" | Known issues | | style="background:silver" | Known issues | ||
| | | | ||
− | ICA-AtoM (v0.6) | + | 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" | |- valign="top" align="left" | ||
| style="background:silver" | Use cases | | style="background:silver" | Use cases | ||
| | | | ||
− | [[USC-1.2.1 | USC-1.2.1 Implement an arrangement policy | + | [[USC-1.2.1 | USC-1.2.1 Implement an arrangement policy]] |
|- valign="top" align="left" | |- valign="top" align="left" |
Revision as of 11:44, 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 > Functional requirements > FNC-1 Implement a system of control > FNC-1.2 Implement a system of intellectual control > FNC-1.2.1 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 |
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. |
Context (parent requirements) | |
Source quotation | |
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 the ParentLevel field. A description is recognized as the highest level when the ParentLevel field is blank. "Discrete items" (items not linked to a higher parent level) are permitted: simply leave the ParentLevel blank. |
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. |
Use cases | |
User Manual sections |
Add / edit content > Archival descriptions > Edit screen (data entry) > Identity area |