Qubit Input / Export - Dublin Core

Main Page > BCAUL Pilot Project > Metadata Mapping > Qubit Input / Export - Dublin Core


 * Contents: Purpose | Analysis | Mapping | Taxonomies
 * Document status: in progress
 * Last updated: 5 Dec 2008.

Purpose
Map Dublin Core elements to Qubit fields to support:
 * OAI harvesting (output as Dublin Core xml).
 * Design of Dublin Core data entry templates (input).

A design goal of Qubit is to fully support simple Dublin Core, ensuring that DC elements map to core Qubit objects and properties (fields).

Analysis
Simple DC comprises 15 elements. In mapping these to the current Qubit (1.0.4), elements fall into 3 groups:
 * Core: There is a one-to-one relation between a DC element and a field in Qubit's information_object table.
 * Relations: Qubit stores data corresponding to a DC element in related records residing outside of the information_object table.
 * Custom fields: Qubit can only store data corresponding to a DC element via "custom fields", i.e. by creating related records in the property table.

Ideally, no DC elements should be handled as custom fields but should be moved to the core information_object fields or handled via relations.

Taxonomies
DC event types
 * Created
 * Published
 * Contributed
 * Valid over
 * Made available
 * Modified
 * Accepted
 * Copyrighted
 * Submitted

DC resource types

See DCMI Type Vocabulary:
 * Collection
 * Dataset
 * Event
 * Image
 * Interactive resource
 * Moving image
 * Physical object
 * Service
 * Software
 * Sound
 * Still image
 * Text

DC relation types
 * Is source of
 * Has source in
 * Is version of
 * Has version
 * Is replace by
 * Replaces
 * Is required by
 * Requires
 * Is part of
 * Has part
 * Is referenced by
 * References
 * Is format of
 * Has format
 * Conforms to

Create the following taxonomies, either empty or with sample data, as place-holders for local taxonomies:
 * DC audience types
 * DC instructional methods
 * DC accrual methods
 * DC accrual periodicity
 * DC accrual policy