Difference between revisions of "Metadata requirements"

From ICA-AtoM
Jump to navigation Jump to search
 
(63 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Main page]] > [[System Requirements]] > Metadata requirements
+
[[Main Page]] > [[System requirements]] > Metadata requirements
  
 +
== Purpose ==
  
Metadata requirements identify the kinds of information the system must capture in order to do the things specified by the functional requirements.  
+
Metadata requirements identify the entities the system must track and the kinds of information about them it must capture in order to do the things specified by the [[Functional requirements|functional requirements]]. The requirements provide:
== Archival descriptions ==
 
  
=== Identity area ===
+
*Parameters for designing the system.
  
==== Reference code ====
+
*Criteria for testing the system (used in initial release and future iterations and upgrades).
  
{| border="1" cellpadding="2"
+
*Planning guidelines for developing the system (identify data not currently captured).
  
|- valign="top" align="left" style="background:#00008B; color:white"
+
*Documentation for standards compliance (link requirements to relevant international or national descriptive standards).
!width="250" | Element name
 
!width="700" | Reference code
 
  
|- valign="top" align="left"
 
| style="background:silver"  | Requirement specification
 
| The system must:
 
*Describe archival materials at multiple levels reflecting the levels of arrangement.
 
*Let institutions determine the number of levels of description allowed or required.
 
  
|- valign="top" align="left"
+
== Organization ==
| style="background:silver" | Requirement quotation
 
|
 
*[[ISAD(G)# | ISAD(G) I.8]]
 
*[[ISAD(G)# | ISAD(G) 1.1]]
 
*[[OSARIS)# | OSARIS 2.1]]
 
  
|- valign="top" align="left"
+
Metadata requirements are organized hierarchically, with high-level requirements broken down into sub- and sub-sub-requirements. To facilitate cross-references and links, each requirement has been assigned an alpha-numeric code: the alpha prefix designates the type of requirement (MR = mateadata requirement), the number establishes its position in the hierarchy. Seven main metadata requirements have been identified:
| style="background:silver" | Associated metadata requirements
 
|
 
*[[Archival materials#Level of description | Archival materials: Level of description]]
 
*[[Archival materials#Next upper level of description | Archival materials: Next upper level of description]]
 
  
|- valign="top" align="left"
+
*[[MR-1|MR-1 Record information about archival materials]]
| style="background:silver" | Associated usability requirements
 
|
 
*Provide drop-down lists for user to select from available levels.
 
*Display current level of description clearly on screen.
 
*Display context of arrangement clearly on screen (current description's position in the hierarchy of arrangement).
 
  
|- valign="top" align="left"
+
*[[MR-2|MR-2 Record information about actors]]
| style="background:silver" | ICA-AtoM implementation
 
|  
 
*By default ICA-AtoM allows for description at fonds, sub-fonds, series, sub-series, file, and item level.
 
*Institutions can determine how many sub-levels to allow for series.
 
*System administrators can customize ''Level of description'' value list to include all permitted levels of description.
 
  
|- valign="top" align="left"
+
*[[MR-3|MR-3 Record information about archival institutions]]
| style="background:silver" | User Manual sections
 
|
 
*How to assign levels of description.
 
*How to link a description to higher and lower levels.
 
  
|}
+
*[[MR-4|MR-4 Record information about controlled terms]]
  
---
+
*[[MR-5|MR-5 Record information about descriptions]]
  
== Authority records ==
+
*[[MR-6|MR-6 Record information about relationships between descriptions]]
  
 +
*[[MR-7|MR-7 Record information about users]]
  
  
== Archival institutions ==
+
== Information ==
 +
 
 +
Each metadata requirement includes some or all of the following information:
 +
 
 +
*'''Requirement number''': MR-x.x.x, unique tracking number assigned to requirement.
 +
 
 +
*'''Requirement name''': descriptive name assigned to requirement.
 +
 
 +
*'''Specification''': brief description of requirement; what data must the application be able to capture?
 +
 
 +
*'''Context (parent requirements)''': links to higher-level metadata requirements, if applicable.
 +
 
 +
*'''Sub-requirements''': links to lower-level metadata requirements, if applicable.
 +
 
 +
*'''Source quotations''': links to standards or other documents: why must the application capture this data.
 +
 
 +
*'''Associated functional requirements''': what functionality requires the application to capture this data.
 +
 
 +
*'''Associated quality requirements''': what design and interface features must the application have to capture the data ''well''.
 +
 
 +
*'''Associated technical requirements''': what system architecture, hardware / software configurations, and programming rules must the application implement to capture the data.
 +
 
 +
*'''ICA-AtoM implementation''': what fields in ICA-AtoM store the data.
 +
 
 +
*'''Known issues''': brief indication of known problems or limitations in the current version of ICA-AtoM that should be addressed in future releases.
 +
 
 +
*'''Use cases''': links to descriptions of user-end scenarios relating to the requirement and how they are handled in ICA-AtoM.
 +
 
 +
*'''User Manual sections''': links to the User manual sections that provide step-by-step instructions for capturing the data.
 +
 
 +
 
 +
Note that most of this detail will only be found at the lower-level requirements. Higher-level requirements will typically only include the requirement name, number, specification, and source quotation, with links to the lower-level sub-requirements.
 +
 
 +
 
 +
== Index of metadata requirements ==
 +
 
 +
The following is the full index to all metadata requirements identified to date.
 +
 
 +
[[MR-1|'''MR-1 Record information about archival materials''']]
 +
 
 +
*[[MR-1.1 |MR-1.1 Register units of description]]
 +
**[[MR-1.1.1|MR-1.1.1 Assign unique identifiers to a description]]
 +
**[[MR-1.1.2|MR-1.1.2 Assign names to the object of a description]]
 +
**[[MR-1.1.3|MR-1.1.3 Indicate the level of description]]
 +
**[[MR-1.1.4|MR-1.1.4 Indicate the dates of the material described]]
 +
**[[MR-1.1.5|MR-1.1.5 Indicate the extent of the material described]]
 +
 
 +
*[[MR-1.2|MR-1.2 Record information about the context of archival materials]]
 +
**[[MR-1.2.1|MR-1.2.1 Indicate the creator(s) of archival materials]]
 +
**[[MR-1.2.2|MR-1.2.2 Describe the creator(s) of archival materials]]
 +
**[[MR-1.2.3|MR-1.2.3 Describe the custody of archival materials]]
 +
 
 +
*[[MR-1.3|MR-1.3 Record information about the content and structure of archival materials]]
 +
**[[MR-1.3.1|MR-1.3.1. Describe the scope and content of archival materials]]
 +
**[[MR-1.3.2|MR-1.3.2. Describe the appraisal, destruction and scheduling of archival materials]]
 +
**[[MR-1.3.3|MR-1.3.3 Indicate future accruals to archival materials]]
 +
**[[MR-1.3.4|MR-1.3.4 Describe the system of arrangement of archival materials]]
 +
 
 +
*[[MR-1.4|MR-1.4 Record information about the conditions of access and use of archival mtrls]]
 +
**[[MR-1.4.1|MR-1.4.1 Indicate the conditions governing access to archival materials]]
 +
**[[MR-1.4.2|MR-1.4.2 Indicate the conditions governing reproduction of archival material]]
 +
**[[MR-1.4.3|MR-1.4.3 Indicate languages and scripts employed in archival materials]]
 +
**[[MR-1.4.4|MR-1.4.4 Indicate physical characteristics and technical requirements affecting availability of archival materials]]
 +
**[[MR-1.4.5|MR-1.4.5 Indciate the existence of other finding aids to archival materials]]
 +
 
 +
*[[MR-1.5|MR-1.5 Record information about materials related to the unit of description]]
 +
**[[MR-1.5.1|MR-1.5.1 Indicate the location of the originals of the archival materials described]]
 +
**[[MR-1.5.2|MR-1.5.2 Indicate the location of copies of the archival materials described]]
 +
**[[MR-1.5.3|MR-1.5.3 Indicate related archival materials in other units of description]]
 +
**[[MR-1.5.4|MR-1.5.4 Indicate publications related to the archival materials described]]
 +
 
 +
 
 +
[[MR-2|'''MR-2 Record information about actors''']]
 +
 
 +
 
 +
[[MR-3|'''MR-3 Record information about archival institutions''']]
 +
 
 +
 
 +
[[MR-4|'''MR-4 Record information about controlled terms''']]
 +
 
 +
 
 +
[[MR-5|'''MR-5 Record information about descriptions''']]
 +
 
 +
 
 +
[[MR-6|'''MR-6 Record information about relationships between descriptions''']]
 +
 
 +
 
 +
[[MR-7|'''MR-7 Record information about users''']]

Latest revision as of 13:04, 11 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.

Main Page > System requirements > Metadata requirements

Purpose

Metadata requirements identify the entities the system must track and the kinds of information about them it must capture in order to do the things specified by the functional requirements. The requirements provide:

  • Parameters for designing the system.
  • Criteria for testing the system (used in initial release and future iterations and upgrades).
  • Planning guidelines for developing the system (identify data not currently captured).
  • Documentation for standards compliance (link requirements to relevant international or national descriptive standards).


Organization

Metadata requirements are organized hierarchically, with high-level requirements broken down into sub- and sub-sub-requirements. To facilitate cross-references and links, each requirement has been assigned an alpha-numeric code: the alpha prefix designates the type of requirement (MR = mateadata requirement), the number establishes its position in the hierarchy. Seven main metadata requirements have been identified:


Information

Each metadata requirement includes some or all of the following information:

  • Requirement number: MR-x.x.x, unique tracking number assigned to requirement.
  • Requirement name: descriptive name assigned to requirement.
  • Specification: brief description of requirement; what data must the application be able to capture?
  • Context (parent requirements): links to higher-level metadata requirements, if applicable.
  • Sub-requirements: links to lower-level metadata requirements, if applicable.
  • Source quotations: links to standards or other documents: why must the application capture this data.
  • Associated functional requirements: what functionality requires the application to capture this data.
  • Associated quality requirements: what design and interface features must the application have to capture the data well.
  • Associated technical requirements: what system architecture, hardware / software configurations, and programming rules must the application implement to capture the data.
  • ICA-AtoM implementation: what fields in ICA-AtoM store the data.
  • Known issues: brief indication of known problems or limitations in the current version of ICA-AtoM that should be addressed in future releases.
  • Use cases: links to descriptions of user-end scenarios relating to the requirement and how they are handled in ICA-AtoM.
  • User Manual sections: links to the User manual sections that provide step-by-step instructions for capturing the data.


Note that most of this detail will only be found at the lower-level requirements. Higher-level requirements will typically only include the requirement name, number, specification, and source quotation, with links to the lower-level sub-requirements.


Index of metadata requirements

The following is the full index to all metadata requirements identified to date.

MR-1 Record information about archival materials


MR-2 Record information about actors


MR-3 Record information about archival institutions


MR-4 Record information about controlled terms


MR-5 Record information about descriptions


MR-6 Record information about relationships between descriptions


MR-7 Record information about users