Difference between revisions of "Template:Classic RAD"
Line 11: | Line 11: | ||
#Map RAD elements onto existing Qubit fields, relying on the Qubit '''note''' and '''event''' tables to handle anomalies. | #Map RAD elements onto existing Qubit fields, relying on the Qubit '''note''' and '''event''' tables to handle anomalies. | ||
− | 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 | + | 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. |
<br clear="right"> | <br clear="right"> | ||
+ | |||
== Identity area == | == Identity area == | ||
Revision as of 12:34, 28 August 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 > Templates > Classic RAD (1)
Document status: in progress
Structure
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:
- Create custom fields via the Qubit property table; or
- Map RAD elements onto existing Qubit fields, relying on the Qubit note and event tables to handle anomalies.
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
This div has no RAD equivalent. It brings together minimum data entry requirements and Qubit fields which have no RAD analogs. The fields relate to uniquely identifying the unit of description and the name is based on analogy to the ISAD(G) area.
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
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). These elements are then concatenated into a single title statement, with punctuation rules to distinguish the various components. There are several options for implementing this in Qubit. RAD also includes 6 separate Note area elements for notes relating to titles (1.8B1 - 1.8B6).
Option 1: full RAD
Handle RAD elements as custom fields (field name and value stored in related Qubit property records). A getRADTitle() method returns the full title on the View screen, formatted according to RAD punctuation rules.
Title proper
- RAD: 1.1B Title proper
- ISAD(G): na
- Qubit: property::name="title_proper" value=""
- Repeating? NO
General material designation
- RAD: 1.1C General material designation
- ISAD(G): na
- Qubit: property::name="gmd" value=""
- 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: information_object::alternate_title
- Repeating? NO
- Note: Multiple parallel titles can be entered as separate lines in Qubit's single text field or using RAD's punctuation rules.
Other title information
- RAD: 1.1E Other title information
- ISAD(G): na
- Qubit: property::name="other_title_information" value=""
- Repeating? NO
Statements of responsibility
- RAD: 1.1F Statements of responsibility
- ISAD(G): na
- Qubit: property::name="statement_of_responsibility" value=""
- Repeating: YES
Option 2: minimal RAD
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
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
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
Creation context
Physical description area
Publisher's series area
Archival description area
Notes area
Access points