Difference between revisions of "Template:Classic RAD - Class specific"
Line 38: | Line 38: | ||
== Class of material specific details area == | == Class of material specific details area == | ||
− | [[Image: | + | [[Image:tmplClassicRADClassMaterialSpecific1.png|500px|right|thumb|Option 1: separate div displaying each field]] |
− | [[Image: | + | [[Image:tmplClassicRADClassMaterialSpecific2.png|500px|right|thumb|Option 2: separate div showing only fields as needed]] |
This div corresponds to RAD area 1.3. It is used only with certain special media: catrographic materials (5.3 Mathematical data area – 3 elements), architectural and technical drawings (6.3 Scale area – 1 element), and philatelic records (13.3 Issue data area – 2 elements). None of these elements have direct ISAD(G) or Qubit analogs. The main options are to implement as custom fields or assimilate to Qubit '''notes'''. | This div corresponds to RAD area 1.3. It is used only with certain special media: catrographic materials (5.3 Mathematical data area – 3 elements), architectural and technical drawings (6.3 Scale area – 1 element), and philatelic records (13.3 Issue data area – 2 elements). None of these elements have direct ISAD(G) or Qubit analogs. The main options are to implement as custom fields or assimilate to Qubit '''notes'''. |
Revision as of 15:53, 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
Template: Classic RAD
|
Title and statement of responsibility area |
Class of material specific details area
This div corresponds to RAD area 1.3. It is used only with certain special media: catrographic materials (5.3 Mathematical data area – 3 elements), architectural and technical drawings (6.3 Scale area – 1 element), and philatelic records (13.3 Issue data area – 2 elements). None of these elements have direct ISAD(G) or Qubit analogs. The main options are to implement as custom fields or assimilate to Qubit notes.
Option 1
- Map RAD elements to Qubit custom fields (storing field names and values in Qubit property records related to the information object).
- Include fields on the interface for each field.
Option 2
- Same as (1) except do not include each field on interface, only on an "as-needed" basis.
- Use a drop-down list controlled by a "Class of material specific details" taxonomy of RAD element names.
Option 3
- Map RAD elements to Qubit notes, using "Class of material specific details" taxonomy to control note types by RAD element names.
- Eliminate Class of material specific details area as separate div, since it is handled by Notes area.
- Or, retain as separate div displaying only this type of note.
RAD elements:
Statement of scale
- RAD: 5.3B (cartographic materials), 6.3B (architectural and technical drawings)
- ISAD(G): na
- Qubit: property::name="statement_of_scale" value=" " (option1/2); note::type="class_of_material_specific_detail" qualifier="statement_of_scale" content=" " (option3).
- Repeating? NO
Statement of projection
- RAD: 5.3C
- ISAD(G): na
- Qubit: property::name="statement_of_projection" value=" " (option1/2); note::type="class_of_material_specific_detail" qualifier="statement_of_projection" content=" " (option3).
- Repeating? NO
Statement of coordinates
- RAD: 5.3D
- ISAD(G): na
- Qubit: property::name="statement_of_coordinates" value=" " (option1/2); note::type="class_of_material_specific_detail" qualifier="statement_of_coordinates" content=" " (option3).
- Repeating? NO
Issuing jurisdiction / denomination
- RAD: 12.3B, 12.3C
- ISAD(G): na
- Qubit: property::name="issuing_jurisdiction_denomination" value=" " (option1/2); note::type="class_of_material_specific_detail" qualifier="issuing_jurisdiction_denomination" content=" " (option3).
- Repeating? YES
- Note: Combines two separate RAD elements because these often have a 1-to-many relationship, e.g. "Canada : 4 cents, 40 cents".