Difference between revisions of "Report: final report data elements"
| Line 29: | Line 29: | ||
== Findings == | == Findings == | ||
| − | === Research / data mapping === | + | === Research / data mapping crosswalk === |
| + | |||
| + | ''What'' | ||
Crosswalks establish relationships of equivalence between data elements in two or more standards. | Crosswalks establish relationships of equivalence between data elements in two or more standards. | ||
| + | |||
| + | ''Why'' | ||
Practical purpose: required when an application built around one standard needs to interact with data structured according to other standards. | Practical purpose: required when an application built around one standard needs to interact with data structured according to other standards. | ||
| Line 37: | Line 41: | ||
*Export: output data in form structured by different standard, typically for use by application built on that standard. | *Export: output data in form structured by different standard, typically for use by application built on that standard. | ||
*Design: expand user base of application by adapting it to other descriptive communities (use different standards to describe same or different types of materials). | *Design: expand user base of application by adapting it to other descriptive communities (use different standards to describe same or different types of materials). | ||
| + | |||
| + | ''Import'' and ''export'' involve devising rules for handling data and implementing these as methods or scripts in the application. ''Design'' addresses both database architecture (more tables or fields needed?) and user interface (layouts / forms for data entry and presentation). | ||
| + | |||
| + | ''Which standards'' | ||
The BCAUL project involved each of these scenarios. | The BCAUL project involved each of these scenarios. | ||
*ICA-AtoM is built around ICA descriptive standards. | *ICA-AtoM is built around ICA descriptive standards. | ||
*The application needs to be able to import and export data in a number of exchange standards: EAD, MARC21, MODS. | *The application needs to be able to import and export data in a number of exchange standards: EAD, MARC21, MODS. | ||
| − | *The software must be adapted to Canadian descriptive standards (RAD). | + | *The software must be adapted to Canadian descriptive standards (RAD) for use by Canadian archivists. |
| − | + | ||
| + | While outside of the scope of the BCAUL project, it should be noted that the underlying software on which ICA-AtoM is based (Qubit) is intended as a metadata toolkit for describing collections of information objects, including archival materials, but also museum artefacts, works of arts, and publications. These other, non-archival types of material may require other descriptive standards and crosswalk work has included Dublin Core | ||
=== Installation === | === Installation === | ||
Revision as of 17:39, 23 September 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 > BCAUL pilot project > Reports
Background to BCAUL
History and development
Why upgrade?
- Multi-level description
- More efficient upload from institutions to BCAUL
- Long-term sustainability
Canadian archival network: context / directions / concerns
- See CCA / LAC Capacity Assessment Study
Project review
Objective
Partners
Funding
Activities
Outcome
Findings
Research / data mapping crosswalk
What
Crosswalks establish relationships of equivalence between data elements in two or more standards.
Why
Practical purpose: required when an application built around one standard needs to interact with data structured according to other standards.
- Import: take in data originally structured by a different standard.
- Export: output data in form structured by different standard, typically for use by application built on that standard.
- Design: expand user base of application by adapting it to other descriptive communities (use different standards to describe same or different types of materials).
Import and export involve devising rules for handling data and implementing these as methods or scripts in the application. Design addresses both database architecture (more tables or fields needed?) and user interface (layouts / forms for data entry and presentation).
Which standards
The BCAUL project involved each of these scenarios.
- ICA-AtoM is built around ICA descriptive standards.
- The application needs to be able to import and export data in a number of exchange standards: EAD, MARC21, MODS.
- The software must be adapted to Canadian descriptive standards (RAD) for use by Canadian archivists.
While outside of the scope of the BCAUL project, it should be noted that the underlying software on which ICA-AtoM is based (Qubit) is intended as a metadata toolkit for describing collections of information objects, including archival materials, but also museum artefacts, works of arts, and publications. These other, non-archival types of material may require other descriptive standards and crosswalk work has included Dublin Core