Template:Classic RAD - Revision history

Richard: /* Overview */

2008-09-03T20:28:36Z

Overview

Richard at 20:27, 3 September 2008

2008-09-03T20:27:11Z

Richard: /* Standard number area */

2008-09-03T17:57:45Z

Standard number area

Richard: /* Access points */

2008-09-03T17:56:50Z

Access points

Richard: /* Notes area */

2008-09-03T17:56:29Z

Notes area

Richard at 17:38, 3 September 2008

2008-09-03T17:38:51Z

Richard at 17:35, 3 September 2008

2008-09-03T17:35:16Z

Richard: /* Notes area */

2008-09-03T17:33:36Z

Notes area

Richard at 17:08, 3 September 2008

2008-09-03T17:08:30Z

Richard: /* Publisher's series area */

2008-09-03T17:02:24Z

Publisher's series area

@@ Line 51: / Line 51: @@
 [[Image:tmplClassicRADStructure1.png|500px|right|thumb|Divs used to organize data entry screen]]
-This template is modelled closely on the Canadian ''Rules for Archival Description'' (RAD). The divs that structure the data entry screen are drawn from RAD areas of description, with additional divs to handle Qubit-required fields / implementations that have no RAD equivalent.
+The purpose of this template is to provide an interface that mirrors as closely as possible the Canadian ''Rules for Archival Description'' (RAD). The divs that structure the data entry screen are drawn from RAD areas of description, with additional divs to handle Qubit-required fields / implementations that have no RAD equivalent.
 RAD in turn contains a number of elements that have no ISAD(G) or Qubit analogs. There are two basic approaches for handling these:
@@ Line 61: / Line 61: @@
 <br clear="right">
 == Identity area ==

← Older revision		Revision as of 20:27, 3 September 2008
Line 10:		Line 10:
	=== Classic RAD template ===		=== Classic RAD template ===

−	''Document status: ~~in progress~~''	+	''Document status: draft (3 Sep 2008)''

@@ Line 305: / Line 305: @@
 '''Option 3'''
-*Map to Qubit ''Identifier'' when needed, using Qubit '''note''' if required.
+*Eliminate both ''Standard number'' field and div.
-*Eliminate ''Standard number area'' since data is handled by ''Identity area'' field.
+*Map to Qubit ''Identifier'' when needed, using Qubit '''note''' to elaborate if required.
 <br clear="right">
 == Access points ==

@@ Line 308: / Line 308: @@
 *Eliminate ''Standard number area'' since data is handled by ''Identity area'' field.
 == Access points ==
@@ Line 333: / Line 334: @@
 <br clear="right">
 == Control area / Digital object / Storage location ==

← Older revision		Revision as of 17:56, 3 September 2008
Line 287:		Line 287:

	<br clear="right">		<br clear="right">
		+	== Standard number area ==
		+
		+	[[Image:tmplClassicRADStandardNumber1.png\|500px\|right\|thumb\|Option 1: custom field, own div]]
		+
		+	[[Image:tmplClassicRADStandardNumber2.png\|500px\|right\|thumb\|Option 2: custom field, moved to Identity area div]]
		+
		+	This div corresponds to RAD area 1.9, ''Standard number area''. It includes only one element: ''Standard number'' (1.9B), applicable only at the item level for international standard numbers (e.g. ISBNs, ISSNs).
		+
		+
		+	'''Option 1'''
		+	*Create a custom Qubit field as needed ('''property''' table, name="Standard number" value-" ").
		+
		+
		+	'''Option 2'''
		+	*Same as option 1, but move to ''Identity area'' and eliminate ''Standard number area'' as a separate div.
		+
		+
		+	'''Option 3'''
		+	*Map to Qubit ''Identifier'' when needed, using Qubit '''note''' if required.
		+	*Eliminate ''Standard number area'' since data is handled by ''Identity area'' field.
		+
	== Access points ==		== Access points ==

← Older revision		Revision as of 17:38, 3 September 2008
Line 314:		Line 314:
	== Control area / Digital object / Storage location ==		== Control area / Digital object / Storage location ==

−	Implement ~~these areas~~ as in ISAD(G) template.	+	[[Image:tmplClassicRADCommon1.png\|500px\|right\|thumb\|Implement as in ISAD(G) template]]
		+
		+	These divs contains elements that have no RAD analogs (for record control) or fields required for Qubit-specific implementations (digital object and physical object storage). These can all be implemented the same as the ISAD(G) template.

← Older revision		Revision as of 17:35, 3 September 2008
Line 309:		Line 309:
	'''Option 2'''		'''Option 2'''
	*Implement the same as ISAD(G) template, i.e. allowing ''Name'', ''Place'' and ''Subject'' access points with no qualifying "types".		*Implement the same as ISAD(G) template, i.e. allowing ''Name'', ''Place'' and ''Subject'' access points with no qualifying "types".
		+
		+
		+	<br clear="right">
		+	== Control area / Digital object / Storage location ==
		+
		+	Implement these areas as in ISAD(G) template.

← Older revision		Revision as of 17:33, 3 September 2008
Line 284:		Line 284:

	This div corresponds to RAD area 1.8, ''Notes area''. RAD includes 30 elements as distinct types of notes in this area. A number of which have analogs in ISAD(G) where they are treated as descriptive elements in their own right rather than "notes". These elements should be mapped to the corresponding Qubit fields, using Qubit '''notes''' only for RAD notes that have no direct equivalents.		This div corresponds to RAD area 1.8, ''Notes area''. RAD includes 30 elements as distinct types of notes in this area. A number of which have analogs in ISAD(G) where they are treated as descriptive elements in their own right rather than "notes". These elements should be mapped to the corresponding Qubit fields, using Qubit '''notes''' only for RAD notes that have no direct equivalents.
		+
		+
		+	<br clear="right">
		+	== Access points ==
		+
		+	[[Image:tmplClassicRADAccessPoints1.png\|500px\|right\|thumb\|Option 1: restrict to RAD-recognized types of access point]]
		+
		+	[[Image:tmplClassicRADAccessPoints2.png\|500px\|right\|thumb\|Option 2: implement as in ISAD(G) template]]
		+
		+	RAD chapter 21 deals with access points. RAD recognizes the following types of access point (see 21.0A3):
		+	*''Provenance'': name of the person(s), family (ies), or corporate body (bodies) responsible for the creation and/or accumulation and use of the unit being described.
		+	*''Author'': person(s), corporate body(ies) responsible for the form and intellectual or artistic content of the unit being described, if different from the creator of that unit.
		+	*''Other non-subject'': e.g. name(s) of custodians, offices held by a person, persons holding office, persons comprising a family, title.
		+
		+	BCAUL supports ''Name'' access points. Archives Canada accommodates ''Subjects'' in addition to ''Names''.
		+
		+
		+	'''Option 1'''
		+	*Restrict access points to forms explicitly recognized by RAD.
		+	*Limit access points to names of Qubit '''actors'''.
		+	*Include field for specifying type of access point (e.g. "Provenance", "Author", "Custodian", "Officer", "Family member").
		+
		+
		+	'''Option 2'''
		+	*Implement the same as ISAD(G) template, i.e. allowing ''Name'', ''Place'' and ''Subject'' access points with no qualifying "types".

← Older revision		Revision as of 17:08, 3 September 2008
Line 276:		Line 276:
	'''Option 3'''		'''Option 3'''
	*Same as option 2, but also move ''Extent'' to this div, eliminating the RAD ''Phyiscal description area'' div (since this has only the ''Extent'' field in it).		*Same as option 2, but also move ''Extent'' to this div, eliminating the RAD ''Phyiscal description area'' div (since this has only the ''Extent'' field in it).
		+
		+
		+	<br clear="right">
		+	== Notes area ==
		+
		+	[[Image:tmplClassicRADNotes1.png\|500px\|right\|thumb\|Notes area: Qubit fields where equivalents exist, Qubit notes for others]]
		+
		+	This div corresponds to RAD area 1.8, ''Notes area''. RAD includes 30 elements as distinct types of notes in this area. A number of which have analogs in ISAD(G) where they are treated as descriptive elements in their own right rather than "notes". These elements should be mapped to the corresponding Qubit fields, using Qubit '''notes''' only for RAD notes that have no direct equivalents.

← Older revision		Revision as of 17:02, 3 September 2008
Line 252:		Line 252:
	*Rely on RAD 1.8B10 (''Publisher's series note'') for any information relating to publisher's series.		*Rely on RAD 1.8B10 (''Publisher's series note'') for any information relating to publisher's series.
	*Eliminate this area as a separate div since data can be handled by the ''Notes'' div.		*Eliminate this area as a separate div since data can be handled by the ''Notes'' div.
		+
		+
		+	<br clear="right">
		+	== Archival description area ==
		+
		+	[[Image:tmplClassicRADArchivalDescription1.png\|500px\|right\|thumb\|Option 1: Admin history field moved out of div]]
		+
		+	[[Image:tmplClassicRADArchivalDescription2.png\|500px\|right\|thumb\|Option 2: Dates of creation moved into div]]
		+
		+	[[Image:tmplClassicRADArchivalDescription3.png\|500px\|right\|thumb\|Option 3: Dates and Extent fields moved into div]]
		+
		+	This div corresponds to RAD area 1.7. This area contains 3 elements: ''Administrative history / biographical sketch'' (1.7B), ''Custodial history'' (1.7C), and ''Scope and content'' (1.7D). Each of these has clear ISAD(G) equivalent. Given the way Qubit implements date ranges (as '''events''' linked to '''actors'''), it makes sense to display the ''Admin history'' field with the creation events / dates.
		+
		+
		+	'''Option 1'''
		+	*Move ''Admin history / bio sketch'' to the ''Creation context'' area.
		+
		+
		+	'''Option 2'''
		+	*Move the date range / creation event fields to this div, eliminating the RAD ''Dates of creation, publication, distribution area'' div.
		+
		+
		+	'''Option 3'''
		+	*Same as option 2, but also move ''Extent'' to this div, eliminating the RAD ''Phyiscal description area'' div (since this has only the ''Extent'' field in it).