Dan: Fix spacing

2015-07-29T18:30:45Z

Fix spacing

Dan: Fix title

2015-07-29T18:29:51Z

Fix title

Dan: Migrate basic page content

2015-07-29T18:29:25Z

Migrate basic page content

New page

{{#pagetitle:BCAUL pilot project - Qubit import / export: Dublin Core}}
[[Main Page]] > [[Development]] > [[Development/Projects]] > [[Development/Projects/BCAUL Pilot]] > [[Development/Projects/BCAUL Pilot/Metadata mapping]] > DC

<admonition type="note">
This is historical development documentation, migrated from the now-defunct Artefactual wiki. The content was first added there on October 30, 2008, and last updated on December 5, 2008. For more information, see the landing page for this development project: [[Development/Projects/BCAUL Pilot|BCAUL Pilot Project]]. The content was moved to the AtoM wiki on July 29, 2015.
</admonition>

__NOTOC__

*'''Contents:''' [[#Purpose|Purpose]] | [[#Analysis|Analysis]] | [[#Mapping|Mapping]] | [[#Taxonomies|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.

{| style="width:100%; border: 1px solid rgb(192, 192, 192);"


|- valign="top" align="left" style="background-color:silver"
!colspan="2"|Core

|- valign="top" style="background-color: rgb(255, 243, 243);"
|title
|maps to '''information_object::'''''title''

|- valign="top" style="background-color: rgb(255, 243, 243);"
|description
|maps to '''information_object::'''''scope_and_content''

|- valign="top" style="background-color: rgb(255, 243, 243);"
|format
|maps to '''information_object::'''''extent_and_medium''

|- valign="top" style="background-color: rgb(255, 243, 243);"
|identifier
|maps to '''information_object::'''''identifier''

|- valign="top" style="background-color: rgb(255, 243, 243);"
|relation
|maps to '''information_object::'''''related_units_of_description''

|- valign="top" style="background-color: rgb(255, 243, 243);"
|rights
|maps to '''information_object::'''''access_conditions'' and '''information_object::'''reproduction_conditions''


|- valign="top" align="left" style="background-color:silver"
!colspan="2"|Relations

|- valign="top" style="background-color: rgb(240, 240, 255);"
|creator
|get from '''actor''' via related '''event''' records, ''type''="creation"

|- valign="top" style="background-color: rgb(240, 240, 255);"
|subject
|get from '''term''' via related '''object_term_relation''' records

|- valign="top" style="background-color: rgb(240, 240, 255);"
|publisher
|get from '''actor''' via related '''event''' records, ''type''="publication"

|- valign="top" style="background-color: rgb(240, 240, 255);"
|contributor
|get from '''actor''' via related '''event''' records, ''type'' is not "creation" or "publication"

|- valign="top" style="background-color: rgb(240, 240, 255);"
|date
|get from related '''event''' records

|- valign="top" style="background-color: rgb(240, 240, 255);"
|coverage
|get from '''term''' via related '''object_term_relation''' records


|- valign="top" align="left" style="background-color:silver"
!colspan="2"|Custom fields

|- valign="top" style="background-color: rgb(255, 243, 243);"
|type
|store as '''property::'''''name''="resource_type" ''value''=" "

|- valign="top" style="background-color: rgb(255, 243, 243);"
|source
|store as '''property::'''''name''="source" ''value''=" "

|- valign="top" style="background-color: rgb(255, 243, 243);"
|language
|store as '''property::'''''name''="information_object_language" ''value''=" "

|}

== Mapping ==

{| style="width:100%; border: 1px solid rgb(192, 192, 192);"


|- valign="top" align="left" style="background-color:silver"
!style="width: 15%"|DC simple
!style="width: 15%"|DC qualified
!Repeating
!Qubit fields
!style="width: 25%"|Input
!style="width: 25%"|Output


|- valign="top" style="background-color: silver"
|colspan="6"|'''Title'''


|- valign="top" style="background-color: rgb(255, 243, 243);"
|Title

<dc:title>

| 

|No

|'''information_object::'''''title''

| 

| 


|- valign="top" style="background-color: rgb(255, 243, 243);"
| 

|Alternative Title

<dcterms:alternative>

|No

|'''information_object::'''''alternate_title''

| 

| 


|- valign="top" style="background-color: silver"
|colspan="6"|'''Creator'''


|- valign="top" style="background-color: rgb(240, 240, 255);"
|Creator

<dc:creator>

| 

|Yes

|'''actor::'''''authorized_form_of_name''

|Input as '''event''', ''type''="creation".

|Get '''actors''' via related creation '''events'''.


|- valign="top" style="background-color: silver"
|colspan="6"|'''Subject'''


|- valign="top" style="background-color: rgb(255, 243, 243);"
|Subject

<dc:subject>

| 

|Yes

|'''term::'''''name''

|Input as subject access point ('''object_term_relation''').

|Get '''terms''' via related related '''object_term_relations'''.


|- valign="top" style="background-color: silver"
|colspan="6"|'''Description'''


|- valign="top" style="background-color: rgb(240, 240, 255);"
|Description

<dc:description>

| 

|No

|'''information_object::'''''scope_and_content''

| 

| 


|- valign="top" style="background-color: rgb(240, 240, 255);"
| 

|Table Of Contents

<dcterms:tableOfContents>

|No

|'''property::'''''name''="table_of_contents"

|Add custom field ('''property''' record).

| 


|- valign="top" style="background-color: rgb(240, 240, 255);"
| 

|Abstract

<dcterms:abstract>

|No

|'''property::'''''name''="abstract"

|Add custom field ('''property''' record).

| 


|- valign="top" style="background-color: silver"
|colspan="6"|'''Publisher'''


|- valign="top" style="background-color: rgb(255, 243, 243);"
|Publisher

<dc:publisher>

| 

|Yes

|'''actor::'''''authorized_form_of_name''

|Input as '''event''', ''type''="publication".

|Get '''actors''' via related publication '''events'''.


|- valign="top" style="background-color: silver"
|colspan="6"|'''Contributor'''


|- valign="top" style="background-color: rgb(240, 240, 255);"
|Contributor

<dc:contributor>

| 

|Yes

|'''actor::'''''authorized_form_of_name''

|Input as '''event''', ''type''="contribution".

|Get any '''actor''' from related '''events''' where ''type'' does NOT equal "creation" or "publication".


|- valign="top" style="background-color: silver"
|colspan="6"|'''Date'''


|- valign="top" style="background-color: rgb(255, 243, 243);"
|Date

<dc:date>

| 

|Yes

|'''event::'''''date_display''

|Input as '''event'''.

|Get creation '''events''' only[?].
*In DC simple, not possible to differentiate types of dates, use date of creation only.


|- valign="top" style="background-color: rgb(255, 243, 243);"

| 

|Date Created

<dcterms:created>

Date Valid

<dcterms:valid>

Date Available

<dcterms:available>

Date Issued

<dcterms:issued>

Date Modified

<dcterms:modified>

Date Accepted

<dcterms:dateAccepted>

Date Copyrighted

<dcterms:dateCopyrighted>

Date Submitted

<dcterms:dateSubmitted>

|Yes

|'''event::'''''date_display'' ''type_id''=" "

|Input as '''events''', using "dc_date_types" taxonomy ''type''.

| Get related '''events''' where ''type_id'' equals ''id'' of terms from "dc_date_types" taxonomy.


|- valign="top" style="background-color: silver"
|colspan="6"|'''Type'''


|- valign="top" style="background-color: rgb(240, 240, 255);"
|Resource Type

<dc:type>

| 

|Yes

|'''property::'''''name''="resource_type"

|Add custom field ('''property''').
*Note that RAD template required similar field (''General material designation'')
*In future iteration, may add as core field of '''information_object'''.

| 


|- valign="top" style="background-color: silver"
|colspan="6"|'''Format'''


|- valign="top" style="background-color: rgb(255, 243, 243);"
|Format

<dc:format>

| 

|Yes

|'''information_object::'''''extent_and_medium''

|Qubit does not support multiple entries.

|rowspan="3"|Qubit data relating to format is stored in a single field (''extent_and_medium'') that cannot be easily normalized into separate ''extent'' and ''medium'' elements, especially at aggregate levels of description (fonds, series, file) where this field may contain multiple extent statements.


|- valign="top" style="background-color: rgb(255, 243, 243);"
| 

|Extent

<dcterms:extent>

|Yes

| 

| 


|- valign="top" style="background-color: rgb(255, 243, 243);"
| 

|Medium

<dcterms:medium>

|Yes

| 

| 


|- valign="top" style="background-color: silver"
|colspan="6"|'''Identifier'''


|- valign="top" style="background-color: rgb(240, 240, 255);"
|Identifier

<dc:identifier>

| 

|No

|'''information_object::'''''identifier''

| 

|Get '''contact_information::'''''country_code'' + '''repository::'''''identifier'' + '''information_object::'''''identifier'' to ensure globally unique identifier.


|- valign="top" style="background-color: rgb(240, 240, 255);"
| 

|Bibliographic Citation

<dcterms:bibliographicCitation>

|No

|'''property::'''''bibliographic_citation''

|Add custom field ('''property''').

| 


|- valign="top" style="background-color: silver"
|colspan="6"|'''Source'''


|- valign="top" style="background-color: rgb(255, 243, 243);"
|Source

<dc:source>

| 

|No

|'''information_object::'''''title''

|Input as a '''relation''' between two '''information_objects''', with ''type''="source".

|Get '''information_object''' from related '''relation''' record where ''type''="source".


|- valign="top" style="background-color: silver"
|colspan="6"|'''Language'''


|- valign="top" style="background-color: rgb(240, 240, 255);"
|Language

<dc:language>

| 

|Yes

|'''property::'''''name''="information_object_language" value=" "

| 

| 


|- valign="top" style="background-color: silver"
|colspan="6"|'''Relation'''


|- valign="top" style="background-color: rgb(255, 243, 243);"
|Relation

<dc:relation>

| 

|No

|'''information_object::'''''related_units_of_description''

|Input into simple text field.
*May include information relating to more than one relation.

|Cannot normalize Qubit data into multiple relation tags.
*In future iteration, Qubit will register relation between '''information_objects''' in '''relation''' table.


|- valign="top" style="background-color: rgb(255, 243, 243);"
| 

|Is Version Of

<dcterms:isVersionOf>

Has Version

<dcterms:hasVersion>

Is Replaced By

<dcterms:isReplacedBy>

Replaces

<dcterms:replaces>

Is Required By

<dcterms:isRequiredBy>

Requires

<dcterms:requires>

Is Part Of

<dcterms:isPartOf>

Has Part

<dcterms:hasPart>

Is Referenced By

<dcterms:isReferencedBy>

References

<dcterms:references>

Is Format Of

<dcterms:isFormatOf>

Has Format

<dcterms:hasFormat>

Conforms To

<dcterms:conformsTo>

|Yes

|'''information_object::'''''title''

|Input as '''relations''' using "dc_relation_type" taxonomy.

|Cannot currently output as DC qualified (interface for registering '''relations''' not yet implemented).


|- valign="top" style="background-color: silver"
|colspan="6"|'''Coverage'''


|- valign="top" style="background-color: rgb(240, 240, 255);"
|Coverage

<dc:coverage>

| 

|Yes

|'''term::'''''name''

|Input as ''place'' and ''historical event'' access points.

|rowspan="3"|
Get '''terms''' from related '''object_term_relations'''.

Note that:
*Historical event terms are also extended as '''historical_event''' objects.
*Place terms are also extended as '''place''' objects.


|- valign="top" style="background-color: rgb(240, 240, 255);"
| 

|Temporal Coverage

<dcterms:temporal>

|Yes

|'''term::'''name''

|Input as historical event access points.


|- valign="top" style="background-color: rgb(240, 240, 255);"
| 

|Spatial Coverage

<dcterms:spatial>

|Yes

|'''term::'''name''

|Input as place access points.


|- valign="top" style="background-color: silver"
|colspan="6"|'''Rights'''


|- valign="top" style="background-color: rgb(255, 243, 243);"
|Rights Management

<dc:rights>

| 

|Yes

|'''information_object::'''''access_conditions''

'''information_object::'''''reproduction_conditions''

|In DC simple, map input to ''access_conditions''. Note that Qubit does not support this as a repeatable element.

|Get ''access_conditions'' + ''reproduction_conditions''.


|- valign="top" style="background-color: rgb(255, 243, 243);"
| 

|Access Rights

<dcterms:accessRights>

|Yes

|'''information_object::'''''access_conditions''

|Input to text field (string).

|Cannot normalize Qubit data (single field) to repeating elements.


|- valign="top" style="background-color: rgb(255, 243, 243);"
| 

|License

<dcterms:license>

|Yes

|'''information_object::'''''reproduction_conditions''

|Input to text field (string).

|Cannot normalize Qubit data (single field) to repeating elements.


|- valign="top" style="background-color: silver"
|colspan="6"|'''Audience'''


|- valign="top" style="background-color: rgb(240, 240, 255);"
| 

|Audience

<dcterms:audience>

|Yes

|'''property::'''''name''="audience" value=" "

|Add as custom field ('''property''') with controlled taxonomy ("audience"); interface should allow multiple values.

| 


|- valign="top" style="background-color: rgb(240, 240, 255);"
| 

|Mediator

<dcterms:mediator>

|No

|'''property::'''''name''="audience_mediator" value=" "

|Add as custom field ('''property''').

| 


|- valign="top" style="background-color: rgb(240, 240, 255);"
| 

|Audience Education Level

<dcterms:educationLevel>

|No

|'''property::'''''name''="audience_education_level" value=" "

|Add as custom field ('''property''').

| 


|- valign="top" style="background-color: silver"
|colspan="6"|'''Provenance'''


|- valign="top" style="background-color: rgb(255, 243, 243);"
| 

|Provenance

<dcterms:provenance>

|No

|'''information_object::'''''archival_history''

| 

| 


|- valign="top" style="background-color: silver"
|colspan="6"|'''Rights holder'''


|- valign="top" style="background-color: rgb(240, 240, 255);"
| 

|Rights Holder

<dcterms:rightsHolder>

|Yes

|'''actor::'''''authorized_form_of_name''

|Input as '''rights''' linking '''information_object''' to '''rights''' object and '''rights''' object to one or more '''actors''' via '''rights_actor_relation''' (interface not yet implemented).

|Get rights holders for '''information_object''' via '''rights''' and '''right_actor_rleation'''.


|- valign="top" style="background-color: silver"
|colspan="6"|'''Instructional method'''


|- valign="top" style="background-color: rgb(255, 243, 243);"
| 

|Instructional Method

<dcterms:instructionalMethod>

|Yes

|'''property::'''''name''="instructional_method" ''value''=" "

|Add as custom field ('''property''') with controlled taxonomy ("instructional_methods"); interface should allow multiple values.

| 


|- valign="top" style="background-color: silver"
|colspan="6"|'''Accruals'''


|- valign="top" style="background-color: rgb(240, 240, 255);"
| 

|Accrual Method

<dcterms:accrualMethod>

|Yes

|'''property::'''''name''="accrual_method" ''value''=" "

|Add as custom field ('''property''') with controlled taxonomy ("accrual_methods"); interface should allow multiple values.

|Get from related '''property''' records where ''name''="accural_method".


|- valign="top" style="background-color: rgb(240, 240, 255);"
| 

|Accrual Periodicity

<dcterms:accrualPeriodicity>

|No

|'''information_object::'''''accruals''

|Input to Qubit text field ''accruals'' with controlled taxonomy ("accrual_periodicity"); cannot be structured as repeating field.


|- valign="top" style="background-color: rgb(240, 240, 255);"
| 

|Accrual Policy

<dcterms:accuralPolicy>

|Yes

|'''property::'''''name''="accrual_policy" ''value''=" "

|Add as custom field ('''property''') with controlled taxonomy ("accrual_policy"); interface should allow multiple values.

|Get from related '''property''' records where ''name''="accural_policy".

|}

== Taxonomies ==

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

'''DC resource types'''

See [http://dublincore.org/documents/dcmi-type-vocabulary/ 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

------

* [[Development/Projects/BCAUL Pilot/Metadata mapping|Back to the BCAUL Metadata mapping page]]
* [[Development/Projects/BCAUL Pilot|Back to BCAUL Pilot landing page]]
* [[Development/Projects|Back to Development projects]]
* [[Main Page|Back to AtoM wiki Main Page]]

[[Category:Development documentation]]

← Older revision		Revision as of 18:29, 29 July 2015
Line 1:		Line 1:
−	{{#pagetitle:BCAUL pilot project - Qubit ~~import~~ / export: Dublin Core}}	+	{{#pagetitle:BCAUL pilot project - Qubit input/export: Dublin Core}}
	[[Main Page]] > [[Development]] > [[Development/Projects]] > [[Development/Projects/BCAUL Pilot]] > [[Development/Projects/BCAUL Pilot/Metadata mapping]] > DC		[[Main Page]] > [[Development]] > [[Development/Projects]] > [[Development/Projects/BCAUL Pilot]] > [[Development/Projects/BCAUL Pilot/Metadata mapping]] > DC

@@ Line 7: / Line 7: @@
 __NOTOC__
 *'''Contents:''' [[#Purpose|Purpose]] | [[#Analysis|Analysis]] | [[#Mapping|Mapping]] | [[#Taxonomies|Taxonomies]]
@@ Line 19: / Line 18: @@
 *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).
@@ Line 29: / Line 29: @@
 *'''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.

Development/Projects/BCAUL Pilot/Metadata mapping/DC - Revision history

Dan: Fix spacing

Dan: Fix title

Dan: Migrate basic page content