Template:Classic RAD

Main Page > BCAUL pilot project > Templates > Classic RAD (1)

Document status: in progress

Structure

Divs used to organize data entry screen

This version of the RAD template follows RAD's areas of description closely. The divs that structure the data entry screen are drawn from RAD areas, with additional divs to handle Qubit-required fields / implementations. RAD contains a number of elements that have no ISAD(G) or Qubit analogs. There are two basic approaches for handling these:

1. Create custom fields via the Qubit property table; or
2. Map RAD elements onto existing Qubit fields, relying on the Qubit note and event tables to handle exceptions.

Approach (1) is most RAD-compliant but it requires more back-end customization to implement fields that are little-used even in RAD environments. Approach (2) requires less customization, but results in loss of RAD-specific information. In many cases a "mixed" approach may be most appropriate. Options are set out and ilustrated below in the relevant RAD area of description.

Identity area

Identity area

This div has no RAD equivalent. It brings together Qubit-required fields that have no RAD analogs. As these fields mainly relate to uniquely identifying the unit of description, the title of this area follows the ISAD(G) equivalent.

Identifier

• RAD: na
• ISAD(G): 3.1.1 Reference code
• Qubit: information_object::identifier
• Repeating? NO
• Notes: At the item-level RAD has a Standard number element (1.9B), but this is used for numbers assigned by international standards bodies (e.g. ISBN number) rather than local institutional reference codes.

Title

• RAD: 1.1B Title proper
• ISAD(G): 3.1.2 Title
• Qubit: information_object::title
• Repeating? NO
• Note: Value returned by method combining elements in Title and statement of responsibility area

Level of description

• RAD: na
• ISAD(G): 3.1.4 Level of description
• Qubit: information_object::level_of_description_id
• Repeating? NO
• Note: No RAD analog but required for Qubit management of the hierarchy of description.

Parent level

• RAD: na
• ISAD(G): na
• Qubit: information_object::parent_id
• Repeating? NO
• Note: No RAD analog but required for Qubit management of the hierarchy of description.

Repository

• RAD: na
• ISAD(G): na
• Qubit: information_object::repository
• Repeating? NO
• Note: No RAD analog but required for Qubit linking of archival description to description of archival insitution holding records.

Title and statement of responsibility area

Option 1

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.
• Use Qubit events for registered RAD Statements of responsibility (1.1F), which only apply at item-level.
• 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.

RAD elements:

Title proper

• RAD: 1.1B
• ISAD(G): na
• Qubit: title::type_id (option1); property::name="title_proper" value=""(option2); information_object::title (option3/4).
• Repeating? NO

General material designation

• RAD: 1.1C
• ISAD(G): na
• Qubit: property::name="gmd" value=""(option1/2/4); submerge in information_object::title (option3).
• Repeating? NO
• Note: drop-down list to controlled list of terms taken from RAD 1.1C.

Parallel title

• RAD: 1.1D Parallel title
• ISAD(G): na
• Qubit: title::title (option1), property::name="parallel_title" value=" " (option2); submerge in information_object::title (option3); information_object::alternate_title (option4).
• Repeating? NO

Other title information

• RAD: 1.1E Other title information
• ISAD(G): na
• Qubit: title::title (option1), property::name="other_title_information" value="" (option2); submerge in information_object::title or note::note (option3/4).
• Repeating? NO

Statements of responsibility

• RAD: 1.1F Statements of responsibility
• ISAD(G): na
• Qubit: property::name="statement_of_responsibility" value="" (option1/2), event::
• Repeating: YES

Option 2: minimal RAD

File:ClassicRAD1 1Identity.png

Identity area

Map all RAD elements to Qubit information_object::title, leaving it to the user to follow RAD content and punctuation rules. This implementation abolishes the Title and statements of responsibility div altogether, since all title information can be handled by the field that appears in the Identity area.

Option 3: mixed

File:ClassicRAD1 3Identity.png

Title and statement of responsibility area

Map RAD Title proper to Qubit information_object::title and RAD Parallel title to Qubit information_object::alternate_title; drop the other RAD title elements (but information relating to them can still be recorded in the Notes area); make no attempt to return a single title statement following RAD punctuation. This implementation can also abolish the Title and statements of responsibility div by adding the Parallel title field to the Identity area div.

Title

• RAD: 1.1B Title proper
• ISAD(G): 3.1.2 Title
• Qubit: information_object::title
• Repeating? NO

Parallel titles

• RAD: 1.1C Parallel title
• ISAD(G): na
• Qubit: information_object::alternate_title
• Repeating? NO
• Note: Multiple parallel titles can be entered on separate lines in Qubit text field.

Edition area

File:ClassicRAD1 1Edition.png

Edition area

This div corresponds to RAD area 1.2. It is used only for item-level description for statements relating to multiple versions of an item and contains 2 elements: Edition statement (1.2B) and Statements of responsibility relating to edition (1.2C).

Neither of these elements have an ISAD(G) or Qubit analog. This implementation handles these element as custom fields (field name and value stored in related Qubit property records). A getRADEdition() method returns the values on the View screen in a single statement formatted by RAD punctuation rules.

Edition statement

• RAD: 1.2B Edition statement
• ISAD(G): na
• Qubit: property::name="edition_statement" value=" "
• Repeating? NO

Statements of responsibility relating to edition

• RAD: 1.2C Statements of responsibility relating to edition
• ISAD(G): na
• Qubit: property::name="statements_of_responsibility_relating_to_edition" value=" "
• Repeating? YES

Class of material specific details

File:ClassicRAD1 1ClassMaterialSpecific.png

Class of material specific details area

Creation context

File:ClassicRAD1 1CreationContext.png

Creation context