Qubit Import - BCAUL Repositories

Main Page > BCAUL Pilot Project > Metadata Mapping > Qubit Import - BCAUL Repositories


 * Contents: Purpose | Mapping | Migation issues
 * Document status: in progress.
 * Last updated: 7 Nov 2008; created on basis of sample data.

Purpose
Existing BCAUL can export repository records using XML tags that correspond to BCAUL database field names. This document maps the BCAUL fields to analogs in Qubit to support bulk import of the data into Qubit.

Mapping
The following table lists each BCAUL field, a sample of the type of data it contains, the corresponding Qubit field, an indication of whether the data should be migrated or not, and notes/comments/explanations.

Migration issues
Structure

1 BCAUL repository record generates:
 * 1 Qubit object (assigns unique Qubit database id)
 * 1 actor (corporate body authority record)
 * 1 repository (description of holdings etc).
 * 1 contact_information (store address data, primary_contact=1).

Repository codes
 * Need policy decision: how to form repository codes.
 * ISDIAH assumes national authority to assign.
 * LAC currently maintains a registry to assign codes for libraries that participates in interlibrary loan programs, includes some archives.

Address
 * BCAUL Address field merges data that is managed in Qubit as separate fields: street_address, city, region (i.e. province), country, postal_code.
 * On import can globally set region="BC", country="Canada".
 * Qubit city maps to BCAUL City.
 * Need method for extracting street_address and postal_code from BCAUL Address.

Repository type
 * Need to harmonize BCAUL and Qubit taxonomies.
 * Need policy decision: retain existing BCAUL value list, replace by default Qubit value list or create new value list.
 * Determine before migration, use appropriate Qubit term ids on import.