Difference between revisions of "Map: RAD to Qubit"

Revision as of 17:16, 11 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 > Import / export maps

Map: RAD to Qubit

Document status: in progress

Contents

1.1 Title and statement of responsibility area

1.2 Edition area

1.3 Class of material specific details area

1.4 Date(s) of creation, including publication, distribution, etc. area

1.5 Physical description area

1.6 Publisher's series area

1.7 Archival description area

1.8 Notes area

1.9 Standard number area

This document maps RAD elements to Qubit fields and methods.

"Repeating" column: Yes = 1 to many relationship between unit of description (information object) and element; No = 1 to 1 relationship.
"Fields" / "Methods" column: multiple values indicates different options for implementing.

RAD	Repeating?	Fields	Methods	Notes
1.1 Title and statement of responsibility area
1.1B Title proper	No	information_object::title	getTitle()	Use new method, getRADTitle() to return all title elements and format by RAD punctuation rules.
1.1C General material designation	Yes	property::scope="gmd" name="information_object_gmd		This is a widely used RAD element; map to property; use with controlled taxonomy drawn from RAD terms; allow multiple values.
1.1D Parallel titles	Yes	information_object::alternate_title note::type="parallel titles and other title information"		Can be handled via Qubit's translation. But note that parallel not just a supplied translation, but appears in title of object itself. If needed, can use Qubit's Alternate title field or require user to put all parallel title info in RAD note (1.8B3).
1.1E Other title information	No	information_object::alternate_title note::type="other title information"		Can use Qubit's Alternate title field or require user to put all other title info in RAD note (1.8B3).
1.1F Statements of responsibility	Yes	event::type="statement of responsibility" actor_role=" "		RAD field used at item-level only; handle as Qubit event.
1.2 Edition area
RAD	Repeating?	Fields	Methods	Notes / recommendations
1.2B Edition statement	No	property::scope="edition" name="information_object_edition_statement" value=" " note::type="edition" content=" "		These RAD fields are used for item-level description only. Qubit information_object:::version refers to version of the description rather than version of object described. If using property for edition statement (1.2B), use event for statement of responsibility (1.2C). Alternatively, can use RAD Note 1.8B7 (Edition) for all info relating to edition.
1.2C Statements of responsibility relating to the edition	Yes	event::type="statement_of_responsibility" actor_role=" " description=" " note::type="edition" content=" "
1.3 Class of material specific details area
RAD	Repeating?	Field	Method	Notes
5.3B Statement of scale (cartographic material)	No	property::scope="material_specific_detail" name="information_object_statement_of_scale" value=" " note::type="statement_of_scale" content=" "		Area applies only to several media (cartographic records, architectural / technical drawings, philatelic records). Prefer property over note: reserve Qubit notes for notes corresponding to RAD Note area elements; there are RAD notes corresponding to these elements.
5.3B Statement of projection (cartographic material)	No	property::scope="material_specific_detail" name="information_object_statement_of_projection" value=" " note::type="statement_of_projection" content=" "
5.3D Statements of coordinates (cartographic material)	No	property::scope="material_specific_detail" name="information_object_statement_of_coordinates" value=" " note::type="statement_of_coordinates" content=" "
6.3B Statement of scale (architectural and technical drawings)	No	property::scope="material_specific_detail" name="information_object_statement_of_scale" value=" " note::type="statement_of_scale" content=" "
12.3B Issuing jurisdiction (philatelic records)	No	property::scope="material_specific_detail" name="information_object_jurisdiction_denomination" value=" " note::type="jurisdiction_denomination" content=" "		Implement these two elements as a single statement / field because their relation is often 1 to many, e.g. "Canada : 4 cents, 40 cents".
12.3C Denomination (philatelic records)	No	property::name="jurisdiction_denomination" value=" " note::type="jurisdiction_denomination" content=" "
1.4 Dates of creation, including publication, distribution, etc. area
RAD	Repeating?	Fields	Methods	Notes
1.4B Date(s) of creation	Yes	event::type="creation \| accumulation" actor_role="creator" description=" "	getDates($eventType="creation")	Allow user to specify type of date (creation, accumulation). At item levels, other types of dates possible (e.g. publication, distribution, manufacture, reproduction, broadcast).
1.4C Place of publication, distribution, etc.	Yes	event::type="publication \| distribution" actor_role="publisher\|distributor" description=" "		Elements 1.4C/D/E/F applicable only at item level. Merge elements into single Qubit event letting user format description according to RAD.
1.4D Name of publisher, distributor, etc	Yes
1.4E Statement of function of publisher, distributor, etc.	Yes
1.4F Date of publication, distribution, etc.	Yes
1.4G Place of manufacture, name of manufacturer, date of manufacture	Yes
1.5 Physical description area
RAD	Repeating?	Field	Method	Notes
1.5B Extent of descriptive unit (including specific material designation)	Yes	information_object::extent_and_medium		Although RAD includes 4 separate elements, .C / .D / .E are all qualifiers of .B and need to accompany it in a single extent statement, e.g. "6 photographs [1.5B] : b&w [1.5C] ; 6 x 6 cm [1.5D] + 1 identification key [1.5E]. Any description can have multiple statements (.B + .C + .D + .E). Map all elements to single Qubit field, leaving it to user to format / punctuation according to RAD rules. In future iterations, it may be useful to remove this data from the information object into a separate extent table (1 to many), with separate fields for the various elements as in RAD; could help automate calculation of extents.
1.5C Other physical details	No
1.5D Dimensions	No
1.5E Accompanying material	No
1.6 Publisher's series area
RAD	Repeating	Field	Method	Notes
1.6 Title proper of publisher's series	No
1.6C Parallel titles of publisher's series	Yes
1.6D Other title information of publisher's series	No
1.6E Statement of responsibility relating to publisher's series	Yes
1.6F Numbering within publisher's series	No
1.7 Archival description area
RAD	Repeating	Field	Method	Notes / recommendations
1.7B Administrative history / biographical sketch	Yes	actor::history
1.7C Custodial history	No	information_object::archival_history
1.7D Scope and content	No	information_object::scope_and_content
1.8 Notes area
RAD	Repeating	Field	Method	Notes
1.8B1 Variations in title	No	note::type="variation in title"
1.8B2 Source of title proper	No	note::type="source of title proper"
1.8B3 Parallel titles and other title information	No	note::type="parallel titles and other title information"
1.8B4 Continuation of title	No	note::type="continuation of title"
1.8B5 Statements of responsibility	No	note::type="statement of responsibility"
1.8B6 Attributions and conjectures	No	note::type="attribution and conjecture"
1.8B7 Edition	No	note::type="edition"
1.8B8 Date(s) of creation	No	note::type="dates_of_creation"
1.8B8a Date(s) of accumulation	No	event::type="accumulation" actor_role="creator"		Record dates of accumulation as Qubit event.
1.8B9 Physical description	No	note::type="physcial description"
1.8B9a Physical condition	No	information_object::physical_characteristics
1.8B9b Conservation	No	note::type="conservation"
1.8B9c Accompanying material	Yes	note::type="accompanying_material"
1.8B10 Publisher's series	No	note::type="publishers series"
1.8B11 Alpha-numeric designations	Yes	note::type="alpha-numeric designations"
1.8B12 Immediate source of acquisition	No	information_object::acquisition
1.8B13 Arrangement	No	information_object::arrangement
1.8B14 Language	Yes	property::information_object_language property::information_object_script
1.8B15a Location of originals	Yes	information_object::location_of_originals
1.8B15b Availability of other formats	Yes	information_object::location_of_copies
1.8B16a Restrictions on access	No	information_object::access_conditions
1.8B16b Rights	No	note::type="rights"
1.8B16c Terms governing use and reproduction	No	information_object::reproduction_conditions
1.8B16d Terms governing publication	No	information_object::reproduction_conditions
1.8B17 Finding aids	Yes	information_object::finding_aids
1.8B18 Associated material	Yes	information_object::related_units_of_description
1.8B19 Accruals	No	information_object::accruals
1.8B20 Related groups of records in different fonds	Yes	information_object::related_units_of_description
1.8B20a Related groups of records within the same fonds	Yes	information_object::related_units_of_description
1.8B21 General note	Yes	note::type="general note"
1.9 Standard number area
RAD	Repeating?	Field	Method	Notes
1.9B Standard number	No

@@ Line 321: / Line 321: @@
-|&nbsp;
+|rowspan="6"|getDates($eventType="creation")
 |Allow user to specify type of date (creation, accumulation).
@@ Line 335: / Line 336: @@
 '''event::'''type="publication | distribution" actor_role="publisher|distributor" description=" "
-|&nbsp;
 |rowspan="5"|Elements 1.4C/D/E/F applicable only at item level.
@@ Line 347: / Line 346: @@
 |- valign="top" style="background-color: rgb(240, 240, 255);" |
 |1.4D Name of publisher, distributor, etc
 |Yes
-|&nbsp;
@@ Line 356: / Line 355: @@
 |1.4E Statement of function of publisher, distributor, etc.
 |Yes
-|&nbsp;
@@ Line 367: / Line 365: @@
 |Yes
-|&nbsp;
@@ Line 379: / Line 375: @@
 |Yes
-|&nbsp;