Difference between revisions of "MTD-1.1.1"
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
| | | | ||
The application must assign one or more unique identifiers (codes) to descriptions. In a multi-repository system (network), the identifier should include include components that uniquely identify the institution that is responsible for the description and its country of origin. | The application must assign one or more unique identifiers (codes) to descriptions. In a multi-repository system (network), the identifier should include include components that uniquely identify the institution that is responsible for the description and its country of origin. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|- valign="top" align="left" | |- valign="top" align="left" | ||
| Line 42: | Line 36: | ||
| style="background:silver" | Associated quality requirements | | style="background:silver" | Associated quality requirements | ||
| | | | ||
| − | Separate database IDs (automatically generated by the application and hidden from user) and reference codes (assigned by the archivist and meaningful to users). | + | *Separate database IDs (automatically generated by the application and hidden from user) and reference codes (assigned by the archivist and meaningful to users). |
| − | Support auto-entry of next available reference code upon record creation. | + | *Support auto-entry of next available reference code upon record creation. |
| − | Automatically concantenate repository's institution and country identifiers with the description reference code to generate a unique identifier in a multi-repository system (user should not have to manually key institution and country codes). | + | *Automatically concantenate repository's institution and country identifiers with the description reference code to generate a unique identifier in a multi-repository system (user should not have to manually key institution and country codes). |
|- valign="top" align="left" | |- valign="top" align="left" | ||
| Line 55: | Line 49: | ||
| style="background:silver" | ICA-AtoM fields | | style="background:silver" | ICA-AtoM fields | ||
| | | | ||
| − | <span class="dbElement">information_object::id</span> | + | *<span class="dbElement">information_object::id</span> |
| − | + | *<span class="dbElement">information_object::identifier</span> | |
| − | <span class="dbElement">information_object::identifier</span> | ||
|- valign="top" align="left" | |- valign="top" align="left" | ||
| style="background:silver" | ICA-AtoM implementation | | style="background:silver" | ICA-AtoM implementation | ||
| | | | ||
| − | ICA-AtoM automatically assigns each record a unqiue database ID (<span class="dbElement">id</span>); this value is invisible to users. | + | *ICA-AtoM automatically assigns each record a unqiue database ID (<span class="dbElement">id</span>); this value is invisible to users. |
| − | Users enter their own <span class="field">Reference code</span> (<span class="dbElement">identifier</span>). ICA-AtoM allows any type of value in this field (numbers, text, alpha-numeric code) to accommodate any institutional system for assigning identifiers. | + | *Users enter their own <span class="field">Reference code</span> (<span class="dbElement">identifier</span>). ICA-AtoM allows any type of value in this field (numbers, text, alpha-numeric code) to accommodate any institutional system for assigning identifiers. |
|- valign="top" align="left" | |- valign="top" align="left" | ||
| style="background:silver" | Known issues | | style="background:silver" | Known issues | ||
| | | | ||
| − | ICA-AtoM (v0.6) cannot currently auto-generate next sequential reference code / number. | + | *ICA-AtoM (v0.6) cannot currently auto-generate next sequential reference code / number. |
|- valign="top" align="left" | |- valign="top" align="left" | ||
| style="background:silver" | Use cases | | style="background:silver" | Use cases | ||
| | | | ||
| − | |||
|- valign="top" align="left" | |- valign="top" align="left" | ||
| Line 83: | Line 75: | ||
[[Add / edit content#Add / edit archival descriptions | Add / edit archival descriptions]] > | [[Add / edit content#Add / edit archival descriptions | Add / edit archival descriptions]] > | ||
| − | [[Add / edit content#Identity area | | + | [[Add / edit content#Identity area | Add / edit content > Archival descriptions > Edit screen (data entry) > Identity area]] |
|} | |} | ||
Revision as of 16:04, 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 > Metadata requirements
- MTD-1 Record information about archival materials
- MTD-1.1 Register units of description
- MTD-1.1.1 Assign unique identifiers to a description
- MTD-1.1 Register units of description
Assign unique identifiers to a description
| Requirement number | MTD-1.1.1 |
|---|---|
| Requirement name | Assign unique identifiers to a description. |
| Requirement specification |
The application must assign one or more unique identifiers (codes) to descriptions. In a multi-repository system (network), the identifier should include include components that uniquely identify the institution that is responsible for the description and its country of origin. |
| Source quotation | |
| Associated functional requirements | |
| Associated quality requirements |
|
| Associated technical requirements | |
| ICA-AtoM fields |
|
| ICA-AtoM implementation |
|
| Known issues |
|
| Use cases | |
| User Manual sections |
Add / edit archival descriptions > Add / edit content > Archival descriptions > Edit screen (data entry) > Identity area |