Difference between revisions of "MTD-1.1.3"

From ICA-AtoM
Jump to navigation Jump to search
Line 1: Line 1:
[[Main Page]] > [[System Requirements]] > [[Metadata requirements]]
+
_NOTOC__
*[[MTD-1 | MTD-1 Record information about archival materials]]
+
<span class="pageTitle">Indicate the level of description</span>
**[[MTD-1.1 | MTD-1.1 Register units of description]]
 
***MTD-1.1.3 Indicate the level of description
 
  
 +
[[Main Page]] > [[System requirements]] > [[Metadata requirements]]
  
== Indicate the level of description ==
 
  
{| border="1" cellpadding="2"
+
'''Specification'''
  
|- valign="top" align="left" style="background:#00008B; color:white"
+
*The system must record information that indicates the unit of description's position within the hierarchy of arrangement.
!width="200" | Requirement number
 
!width="750" | MTD-1.1.3
 
  
|- valign="top" align="left"
 
| style="background:silver" | Requirement name
 
| Indicate the level of description
 
  
|- valign="top" align="left"
+
'''Context (parent requirements)'''
| style="background:silver"  | Requirement specification
 
|
 
The system must be able to:
 
*Identify the unit of description's position within the hierarchy of arrangement.
 
  
|- valign="top" align="left"
+
*[[MR-1|MR-1 Record information about archival materials]]
| style="background:silver" | Source quotation
 
|
 
*[[ISAD(G)#isad3.1.4 | ISAD(G) 3.1.4]]
 
*[[OSARIS#osaris | OSARIS ]]
 
  
|- valign="top" align="left"
+
*[[MR-1.1|MR-1.1 Register units of description]]
| style="background:silver" | Associated functional requirements
 
|
 
*[[FNC-1.2.1 | FNC-1.2.1 Describe material at multiple levels of arrangement]]
 
*[[FNC-2.5.1 | FNC-2.5.1 Identify units of description]]
 
  
|- valign="top" align="left"
 
| style="background:silver" | Associated quality requirements
 
|
 
The application should be able to:
 
*Provide drop-down value list for data entry of <span class="field">Level of description</span>.
 
  
*Provide pick-lists for data entry when specifying unit's position in the hierarhcy of arrangement.
+
'''Source quotation'''
  
|- valign="top" align="left"
+
*[[RS-1#3.4.1|ISAD(G) 3.4.1]]
| style="background:silver" | Associated technical requirements
 
|  
 
  
|- valign="top" align="left"
+
*[[RS-4|OSARIS]]
| style="background:silver" | ICA-AtoM fields
 
|  
 
  
|- valign="top" align="left"
+
 
| style="background:silver" | ICA-AtoM implementation
+
'''Associated functional requirements'''
|
+
*ICA-AtoM includes a <span class="field">Level of description</span> field with a drop-down list for selecting values.  
+
*[[FR-1.2.1|FNC-1.2.1 Describe material at multiple levels of arrangement]]
 +
 
 +
*[[FR-2.5.1|FNC-2.5.1 Identify units of description]]
 +
 
 +
 
 +
'''Associated quality requirements'''
 +
 
 +
*Provide [[Drop-down menu|drop-down menus]] (value lists) for data entry of ''Level of description'' field.
 +
 
 +
*Provide pick-lists for data entry when specifying unit's position in the hierarchy of arrangement.
 +
 
 +
 
 +
'''Associated technical requirements'''
 +
 
 +
 
 +
'''ICA-AtoM fields'''
 +
 
 +
 
 +
'''ICA-AtoM implementation'''
 +
 
 +
*ICA-AtoM includes a ''Level of description'' field with a drop-down list for selecting values.  
  
 
*Value list can be customized by the system <span class="role">administrator</span> to include only levels employed by the institution. The values in this list themselves reside in a separate database table (<span class="entity">Term</span>).
 
*Value list can be customized by the system <span class="role">administrator</span> to include only levels employed by the institution. The values in this list themselves reside in a separate database table (<span class="entity">Term</span>).
Line 60: Line 52:
 
*ICA-AtoM links the current description with others in the hierarchy of arrangement throught the <span class="field">Parent level</span> field in which the user selects the "parent" description (left blank if the description represents the highest level).
 
*ICA-AtoM links the current description with others in the hierarchy of arrangement throught the <span class="field">Parent level</span> field in which the user selects the "parent" description (left blank if the description represents the highest level).
  
|- valign="top" align="left"
 
| style="background:silver" | Known issues
 
|
 
  
|- valign="top" align="left"
+
'''Known issues'''
| style="background:silver" | Use cases
+
 
|
+
 
 +
'''Use cases'''
  
|- valign="top" align="left"
 
| style="background:silver" | User Manual sections
 
|
 
*[[Add / edit archival descriptions#Identity area | Add / edit content > Archival descriptions > Edit screen (data entry) > Identity area]]: steps 9-10.
 
  
|}
+
'''User Manual'''

Revision as of 19:19, 4 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.

_NOTOC__ Indicate the level of description

Main Page > System requirements > Metadata requirements


Specification

  • The system must record information that indicates the unit of description's position within the hierarchy of arrangement.


Context (parent requirements)


Source quotation


Associated functional requirements


Associated quality requirements

  • Provide drop-down menus (value lists) for data entry of Level of description field.
  • Provide pick-lists for data entry when specifying unit's position in the hierarchy of arrangement.


Associated technical requirements


ICA-AtoM fields


ICA-AtoM implementation

  • ICA-AtoM includes a Level of description field with a drop-down list for selecting values.
  • Value list can be customized by the system administrator to include only levels employed by the institution. The values in this list themselves reside in a separate database table (Term).
  • ICA-AtoM links the current description with others in the hierarchy of arrangement throught the Parent level field in which the user selects the "parent" description (left blank if the description represents the highest level).


Known issues


Use cases


User Manual