Template:Classic RAD - Title

From ICA-AtoM
Revision as of 19:06, 28 August 2008 by Richard (talk | contribs)
Jump to navigation Jump to search

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 > Templates

Template: Classic RAD

  • Data entry template following the Canadian Rules for Archival Description

Overview

Title and statement of responsibility area

Edition area

Class of material specific details area

Physical description area

Publisher's series area

Archival description area

Notes area

Standard number area

Control area | Digital object | Storage location

Identity area

Identity area

This div has no RAD equivalent. It brings together Qubit-required fields that have no RAD analogs: Identifier, Level of description, Parent level and Repository. As these fields contribute to uniquely identifying the unit of description, the title of this area follows the ISAD(G) equivalent. Other fields may move into this div if implementation decisions result in some of the other RAD-specific divs being eliminated.



Title and statement of responsibility area

Options 1 and 2
Option 3: title handled by Identity area
Option 4: title handled by expanded Identity area

This div corresponds to RAD area 1.1. Where ISAD(G) has only 1 title element (3.1.2), RAD breaks titles down into 5 elements: Title proper (1.1B), General material designation (1.1C), Parallel titles (1.1D), Other title information (1.1E), and Statements of responsibility (1.1F - applies only at item-level). These elements are then concatenated into a single title statement, with punctuation rules to distinguish the various components. RAD also includes 6 separate Note area elements for notes relating to titles (1.8B1 - 1.8B6). There are several options for implementing this area in Qubit.

Option 1

  • Create a new title table in Qubit to support multiple titles.
  • RAD includes examples of many types of titles (formal, supplied, traditional, alternative, parallel).
  • Table could also track previous titles (if name of fonds / collection has changed over time).
  • Fields could include information_object_id, title, type_id, start_date, end_date.
  • Would also be useful for ISAD(G) template.


Option 2

  • Handle RAD elements as custom fields (field name and value stored in related Qubit property records).
  • Use a getRADTitle() method to return the full title on the View screen, formatted according to RAD punctuation rules.


Option 3

  • Map all RAD element onto the single Qubit field information_object::title.
  • Leave it to user to structure content according to RAD requirements.
  • Use Qubit notes for additonal info relating to title.
  • Abolish Title and statement of responsibility area div since all data is handled by other areas.


Option 4

  • Map RAD Title proper to Qubit information_object::title.
  • Accommodate RAD General material designation (1.1C) as custom field mapped to Qubit property::name="gmd" value=" ".
  • Use Qubit event to register RAD Statements of responsibility.
  • Map all other RAD titles to Qubit information_object::alternate_title.
  • Use Qubit notes to manage any other descriptive info relating to title.
  • Create a "RAD title notes" taxonomy for title notes.
  • Abolish Title and statement of responsibility area div since all data can be handled by other areas.