Difference between revisions of "Descriptive standards"
Jump to navigation
Jump to search
(New page: <span class="pageTitle">Supported descriptive standards</span> Main Page > (UM) User manual > UM-1 System overview > UM-1.4 Supported descriptive standards ...) |
|||
| Line 3: | Line 3: | ||
[[Main Page]] > [[User manual|(UM) User manual]] > [[UM-1 | UM-1 System overview]] > UM-1.4 Supported descriptive standards | [[Main Page]] > [[User manual|(UM) User manual]] > [[UM-1 | UM-1 System overview]] > UM-1.4 Supported descriptive standards | ||
| − | |||
| − | + | While ICA-AtoM is designed around the [http://www.ica.org/ ICA's] international descriptive standards ([[RS-1|ISAD(G)]], [[RS-2|ISAAR(CPF)]], [[RS-3|ISDIAH]]), it is intended to be flexible enough to accommodate other descriptive practices based on other, national or local standards. "Support" here means that users of another standard should be able to use ICA-AtoM to produce outputs that are compliant with that standard. This includes the ability to: | |
| + | |||
| + | * Enter data in fields that represent all of the data elements required by the standard. | ||
| + | |||
| + | * Interact with (view, edit, search) data in ways structured by and labelled according to the terms of the standard. | ||
| + | * Output (print, export) data in formats compliant with the standard. | ||
| − | |||
| − | + | ICA-AtoM accomplishes this through the following design principles: | |
| − | * | + | * Map the data elements of the target standard to the related ICA standard and via this "metadata crosswalk" to the underlying database architecture in ICA-AtoM / [http://qubit-toolkit.org Qubit]. |
| − | + | * Use existing ICA-AtoM fields wherever the crosswalk establishes a direct correlation between elements in the ICA and target standards. | |
| − | |||
| − | |||
| − | * | + | * Create "custom fields" for all other elements in the target standard using ICA-AtoM's '''property''' database table (where ''type''= the name of the element and ''value''= the data itself). |
| − | * | + | * Create additional php methods for managing the data as required. |
| + | * Add data entry / show templates ([[View screen|view]] and [[Edit screen|edit]] screens) using page divisions and field labels based on the structure and terminology of the target standard. | ||
| − | |||
| + | Adding support for other standards requires a system [[Developer|developer]] working on the underlying software code. Once support has been added, however, ICA-AtoM includes an interface for system [[Administrator|administrators]] to easily select and switch between the various standards. | ||
| − | + | * The [http://www.cdncouncilarchives.ca/intro.html Canadian Council of Archives'] ''Rules for Archival Description'' ([http://www.cdncouncilarchives.ca/archdesrules.html RAD]). | |
Revision as of 18:02, 14 November 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.
Supported descriptive standards
Main Page > (UM) User manual > UM-1 System overview > UM-1.4 Supported descriptive standards
While ICA-AtoM is designed around the ICA's international descriptive standards (ISAD(G), ISAAR(CPF), ISDIAH), it is intended to be flexible enough to accommodate other descriptive practices based on other, national or local standards. "Support" here means that users of another standard should be able to use ICA-AtoM to produce outputs that are compliant with that standard. This includes the ability to:
- Enter data in fields that represent all of the data elements required by the standard.
- Interact with (view, edit, search) data in ways structured by and labelled according to the terms of the standard.
- Output (print, export) data in formats compliant with the standard.
ICA-AtoM accomplishes this through the following design principles:
- Map the data elements of the target standard to the related ICA standard and via this "metadata crosswalk" to the underlying database architecture in ICA-AtoM / Qubit.
- Use existing ICA-AtoM fields wherever the crosswalk establishes a direct correlation between elements in the ICA and target standards.
- Create "custom fields" for all other elements in the target standard using ICA-AtoM's property database table (where type= the name of the element and value= the data itself).
- Create additional php methods for managing the data as required.
- Add data entry / show templates (view and edit screens) using page divisions and field labels based on the structure and terminology of the target standard.
Adding support for other standards requires a system developer working on the underlying software code. Once support has been added, however, ICA-AtoM includes an interface for system administrators to easily select and switch between the various standards.
- The Canadian Council of Archives' Rules for Archival Description (RAD).