Report: final report data elements - Revision history

Richard: /* Research / data mapping crosswalk */

2008-09-23T23:51:21Z

Research / data mapping crosswalk

Richard: /* Research / data mapping crosswalk */

2008-09-23T23:39:45Z

Research / data mapping crosswalk

Richard: /* Research / data mapping */

2008-09-23T23:39:17Z

Research / data mapping

Richard: /* Research / data mapping */

2008-09-23T23:01:14Z

Research / data mapping

Richard: /* Research / data mapping */

2008-09-23T22:51:52Z

Research / data mapping

Richard: New page: Main Page > BCAUL pilot project > Reports == Background to BCAUL == === History and development === === Why upgrade? === Multi-level description More efficient upload from...

2008-09-19T16:50:48Z

New page: Main Page > BCAUL pilot project > Reports == Background to BCAUL == === History and development === === Why upgrade? === *Multi-level description *More efficient upload from...

New page

[[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 ===

=== Installation ===

=== Migration ===

=== Uploading ===

=== Direct data entry ===

=== Searching and browsing ===

=== Digitization ===

=== System performance ===

=== Translating ===

=== Printing ===

=== Exporting ===

=== Harvesting ===

=== Documentation ===

=== Training ===

=== System administration ===

== Impact / costs / issues ==

=== Researchers ===

=== Archival institutions ===

=== AABC ===

=== Archives Canada ===

=== Canadian Council of Archives ===

=== Artefactual / ICA-AtoM ===

=== SFU ===

=== UVic ===

=== LAC ===

== Conclusion ==

@@ Line 30: / Line 30: @@
 === Research / data mapping crosswalk ===
 Crosswalks establish relationships of equivalence between data elements in two or more standards.
 Practical purpose: required when an application built around one standard needs to interact with data structured according to other standards.
@@ Line 43: / Line 39: @@
 ''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).
 The BCAUL project involved each of these scenarios.
@@ Line 51: / Line 45: @@
 *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
+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, exhibition supporting material, and publications. These other, non-archival types of material may require other descriptive standards and crosswalk work has included Dublin Core (DC) and the Categories for Descriptions of Works of Art (CDWA).
 === Installation ===

@@ Line 31: / Line 31: @@
 === Research / data mapping crosswalk ===
-''What''
+==== What ====
 Crosswalks establish relationships of equivalence between data elements in two or more standards.

@@ Line 29: / Line 29: @@
 == Findings ==
-=== Research / data mapping ===
+=== Research / data mapping crosswalk ===
 Crosswalks establish relationships of equivalence between data elements in two or more 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.
 *Design: expand user base of application by adapting it to other descriptive communities (use different standards to describe same or different types of materials).
 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).
+*The software must be adapted to Canadian descriptive standards (RAD) for use by Canadian archivists.
-*ICA-AtoM is a branch of Qubit,
 === Installation ===

@@ Line 31: / Line 31: @@
 === Research / data mapping ===
-Crosswalks establish relationships of equivalence between data elements in two or more descriptive, metadata, or data exchange standards.
+Crosswalks establish relationships of equivalence between data elements in two or more standards.
 Practical purpose: required when an application built around one standard needs to interact with data structured according to other standards.
@@ Line 37: / Line 37: @@
 *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).
 === Installation ===

← Older revision		Revision as of 22:51, 23 September 2008
Line 30:		Line 30:

	=== Research / data mapping ===		=== Research / data mapping ===
		+
		+	Crosswalks establish relationships of equivalence between data elements in two or more descriptive, metadata, or data exchange standards.
		+
		+	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).

	=== Installation ===		=== Installation ===

Report: final report data elements - Revision history

Richard: /* Research / data mapping crosswalk */

Richard: /* Research / data mapping crosswalk */

Richard: /* Research / data mapping */

Richard: /* Research / data mapping */

Richard: /* Research / data mapping */

Richard: New page: Main Page > BCAUL pilot project > Reports == Background to BCAUL == === History and development === === Why upgrade? === *Multi-level description *More efficient upload from...

Richard: New page: Main Page > BCAUL pilot project > Reports == Background to BCAUL == === History and development === === Why upgrade? === Multi-level description More efficient upload from...