Differences
This shows you the differences between two versions of the page.
— |
244:rda_relationship_designators [2021/12/29 16:21] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ~~REDIRECT> | ||
+ | |||
+ | ====== RDA Relationship designators ====== | ||
+ | |||
+ | MARC Report 244 adds extensive support for two important lists of RDA Relationship designators that we use in MARC to describe relationships: | ||
+ | |||
+ | * Relationships between a resource and a persons, family, or corporate body associated with the resource (from RDA Appendix I) | ||
+ | * Relationships between works, expressions, | ||
+ | |||
+ | Beginning with version 244, relationship designator support is provided for the following fields/ | ||
+ | |||
+ | |||
+ | ^ MARC ^ RDA ^ | ||
+ | | 100/700 (without $t) **$e** | ||
+ | | 110/710 (without $t) **$e** | ||
+ | | 111/711 (without $t) **$j** | ||
+ | | 700 (with $t) **$i** | ||
+ | | 710 (with $t) **$i** | ||
+ | | 711 (with $t) **$i** | ||
+ | | 730 **$i** | ||
+ | | 787 **$i** | ||
+ | |||
+ | Version 244 also continues to provide validation for $4 (Relator codes) in appropriate headings fields. | ||
+ | |||
+ | We do not provide this support for the series relationship designators, | ||
+ | |||
+ | Validation based on this new relationship support is applied only to ' | ||
+ | |||
+ | We will provide support for subject relationship designators, | ||
+ | |||
+ | ===== Introductory concepts ===== | ||
+ | |||
+ | In MARC, tags and coding alone are usually not explicit enough to indicate specific relationships. The 8XX tags **are** sufficient for the appropriate "In series" | ||
+ | |||
+ | Looking at the subfield coding can tell us a little more. Continuing with the MARC 700 example, if a subfield $t is present, we can at least know that the resource being described is being related to another **resource**. Here, Doyle' | ||
+ | < | ||
+ | 700 1 $aDoyle, Arthur Conan, | ||
+ | |||
+ | Whereas, if a subfield $t is not present in a 700 field, we know that the resource being described is being related to a **person or family**((and if the tag in the example was 710 instead, the relationship would be to a corporate body, and so on)). Here, the described resource (titled: Persuasion) is related in some way to a person named Dothard, Robert L.: | ||
+ | < | ||
+ | 245 10$aPersuasion /$cJane Austen ... | ||
+ | 700 1 $aDothard, Robert L.</ | ||
+ | |||
+ | However, this still does not tell us anything specific about the relationships involved, and this is where the RDA relationship designators step in. | ||
+ | |||
+ | In the first example, we might ask " | ||
+ | |||
+ | RDA provides a way to answer to that question by having us add a relationship designator; as implemented in MARC, we use a subfield $i for resource-to-resource designators: | ||
+ | < | ||
+ | |||
+ | Similarly, in the second example, we might ask "what does Robert Dothard have to do with Persuasion"? | ||
+ | |||
+ | Again, adding a relationship designator sheds light on the nature of the relationship, | ||
+ | < | ||
+ | 245 10$aPersuasion /$cJane Austen ... | ||
+ | 700 1 $aDothard, Robert L.,$ebook designer.</ | ||
+ | | ||
+ | ===== RDA relationship designators in MARC Report ===== | ||
+ | |||
+ | Starting with version 244, MARC Report makes it easy to add, validate, and edit these RDA relationship designators in your records. | ||
+ | |||
+ | To add or edit a relationship designator, you can either type a known term directly after an appropriate subfield code, or you can now use the <F7> function key to choose an appropriate term for that subfield from a pop-up list. | ||
+ | |||
+ | For example, for the " | ||
+ | < | ||
+ | 245 10$aPersuasion /$cJane Austen [...] | ||
+ | 700 1 $aDothard, Robert L.</ | ||
+ | --to add an appropriate relationship designator from a pop-up list for a subfield $e: | ||
+ | |||
+ | * put the cursor at the **end** of the 700 field | ||
+ | * type $e | ||
+ | * press <F7>: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Pressing <F7> presents a list of applicable relationship designators, | ||
+ | |||
+ | * select the designator that you wish to apply from the pop-up list | ||
+ | * press < | ||
+ | |||
+ | MARC Report adds the selected term to the field at the cursor position, and also automatically adjusts preceding and succeeding punctuation: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | (But if you wish to adjust the punctuation manually, go for it! MARC Report will not double-up on the punctuation) | ||
+ | |||
+ | Slightly differently, | ||
+ | * put the cursor at the **beginning** of the field, in front of subfield $a | ||
+ | * type $i | ||
+ | * press <F7> | ||
+ | * select the relationship that you want to add (in the "Hound of the Baskervilles" | ||
+ | * press < | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | __Notes__ | ||
+ | |||
+ | Punctuation, | ||
+ | |||
+ | The pop-up list of relationship designators supports ' | ||
+ | |||
+ | Note that when typing multiple letters, as in ' | ||
+ | |||
+ | NB. The relationship designator list that is used in MARC Report by derived from the RDA Registry. At present, the Registry is not perfectly in sync with the RDA Toolkit. So if a designator is added to the Toolkit (because of ' | ||
+ | |||
+ | |||
+ | ===== RDA Relationship Options ===== | ||
+ | |||
+ | Customization of this new feature is handled on the ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | \\ | ||
+ | |||
+ | Note at the top of the left-panel is an ' | ||
+ | |||
+ | You may use this option as a quick way to switch on/off RDA relationship validation in MARC Report. | ||
+ | |||
+ | Note that this option does not affect the list of terms that appears when pressing <F7> while editing a record, or the more comprehensive documentation that appears when pressing <F1> for MARC Help. | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== MARC-based options ==== | ||
+ | |||
+ | On the left side of the RDA options page, are two groups of MARC tags and subfields for RDA Relationships: | ||
+ | |||
+ | |||
+ | For example, in the Appendix I group, if ' | ||
+ | |||
+ | - Text in 100 subfield $e will be validated against the terms from RDA Appendix I | ||
+ | - Pressing <F7> --while editing subfield $e in tag 100--provides a pop-up list of appropriate terms from RDA Appendix I | ||
+ | |||
+ | On the other hand, if ' | ||
+ | |||
+ | - Text in 100 subfield $e is not validated | ||
+ | - Pressing <F7> --while editing subfield $e in tag 100--has no effect | ||
+ | |||
+ | ---- | ||
+ | |||
+ | **NB. Its important to note that the options here apply both to editing __and__ validation.**((the latter includes both record mode and batch mode)) | ||
+ | |||
+ | ---- | ||
+ | \\ | ||
+ | |||
+ | In addition to the above, there is a separate option for each RDA Appendix that applies only to validation: | ||
+ | Force case-sensitive validation | ||
+ | Since RDA is not particularly concerned about capitalization, | ||
+ | |||
+ | A second option is applied only to the Appendix J terms: | ||
+ | Require colon after subfield $i | ||
+ | This option is on by default and: | ||
+ | |||
+ | * adds a colon after a selected relationship designator, added in subfield $i | ||
+ | * warns about a missing colon in an existing subfield $i | ||
+ | |||
+ | If you are not using a colon as separating punctuation for this data, despite [[http:// | ||
+ | |||
+ | To completely disable MARC Report validation and pop-up lists of RDA relationship designators when editing: | ||
+ | |||
+ | * Go to the RDA page of the options | ||
+ | * Uncheck all of the MARC tag checkboxes on the left panel | ||
+ | |||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== RDA-based options ==== | ||
+ | |||
+ | At the top of the right side of the RDA options page, is another ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | This option provides an interface to a detailed view that makes it possible to control the pop-up lists and validation of the terms from the RDA appendices on a term-by-term by tag basis. | ||
+ | |||
+ | This option uses a similar " | ||
+ | |||
+ | Press ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | \\ | ||
+ | |||
+ | __**How does this work?**__ | ||
+ | |||
+ | Note the column captions beginning with " | ||
+ | |||
+ | For example, at the top of the list is the term " | ||
+ | |||
+ | Using this form, or matrix, you can configure validation and pop-up lists for each RDA relationship individually. | ||
+ | |||
+ | We have, after much research and analysis, determined that not all of the RDA terms are appropriate in all of the MARC tags for which they are possible, and the result of this analysis is the ' | ||
+ | |||
+ | For example, RDA makes it possible to distinguish between ' | ||
+ | * " | ||
+ | * " | ||
+ | * an error message will appear if " | ||
+ | * an error message will appear if " | ||
+ | |||
+ | |||
+ | A much more complex issue is that of the MARC Main entry vs. Added entry concept. For example, " | ||
+ | * " | ||
+ | * an error message will appear if " | ||
+ | |||
+ | __**Customization**__ | ||
+ | |||
+ | Just in case you do not agree with our decisions about the suitability of terms in various MARC headings fields, you can create your own " | ||
+ | |||
+ | * Select 'File | Create new set' | ||
+ | * Enter a name for the new set | ||
+ | * Customize the resulting matrix--which will always begin as a copy of the default set | ||
+ | | ||
+ | To quickly enable or disable all of the checkboxes in the matrix, use the appropriate option from the ' | ||
+ | | ||
+ | Note that disabling all of the checkboxes in the matrix has the same effect as disabling all of the MARC Tag checkboxes on the main options page (as shown here): | ||
+ | |||
+ | {{: | ||
+ | |||
+ | In short, no validation will be performed, and no pop-up list of terms will display when editing. | ||
+ | |||
+ | For best results, uncheck all of the MARC Tag checkboxes on the main RDA options page to disable validation for these relationships completely. | ||
+ | |||
+ | When you are adding or editing relationship designator terms, or validating the work done by others, the Relator matrix that you choose will dictate what is: | ||
+ | * provided as a pop-up list of relationship designator terms that are appropriate for the 100$e, 110$e, 111$j, 700$e, 710$e, 711$j | ||
+ | * given as an error message for relationship designator terms that are not provided in the pop-up lists for the 100$e, 110$e, 111$j, 700$e, 710$e, 711$j | ||
+ | |||
+ | For example, if the default options are in place, then: | ||
+ | * a record containing a tag 100 subfield $e with the term ' | ||
+ | * if you are editing a tag 100 subfield $e, and press <F7>, only those terms that are checked in the matrix as ' | ||
+ | |||
+ | |||
+ | __**Difficulties in MARC usage**__ | ||
+ | |||
+ | Its easy to see how far apart MARC and RDA are when we look closely at some of the MARC usage of subfield $e. | ||
+ | |||
+ | For example: | ||
+ | |||
+ | 100 1 $a Stone, Melicent, $e author, $e illustrator. | ||
+ | | ||
+ | Here we see two concepts, which in RDA require separate statements, joined together in MARC: ' | ||
+ | |||
+ | The practice of joining incompatible RDA properties together like this is provided for by one of those MARC-centric guidelines that many of us never see: | ||
+ | |||
+ | < | ||
+ | PCC Guidelines for the Application of Relationship Designators | ||
+ | in Bibliographic Records | ||
+ | |||
+ | Guideline 10. | ||
+ | |||
+ | If more than one relationship designator is appropriate because the same entity | ||
+ | has multiple roles, preferably use repeating $e (or $j for MARC X11 fields). | ||
+ | If necessary, multiple headings may be used instead. | ||
+ | </ | ||
+ | |||
+ | We have defaulted MARC Report to accept entries like the ' | ||
+ | |||
+ | However, if you wish to be more faithful to RDA, there is a way to achieve this. | ||
+ | |||
+ | When the program is not running, go to your ' | ||
+ | USEPCCWORKAROUND | ||
+ | There is one for validation, and one for editing. To disregard the PCC shortcut, set them both to ' | ||
+ | |||
+ | |||
+ | |||
+ | __**Notes**__ | ||
+ | |||
+ | This version of MARC Report (244) only provides a Relationship editor for terms from RDA Appendix I. There is, currently, no corresponding editor for terms from Appendix J (WEMI to WEMI). We are still assessing the need for this. | ||
+ | |||
+ | In order to support hybrid records, the validation described on this page is applied to both RDA and non-RDA records. If you are not using RDA at all, you may want to disable RDA relationship support on the [[244: | ||
+ | |||
+ | The MARC Relator code, listed in the second column of the matrix, is for reference purposes only, at present. | ||
+ | |||
+ | The subject access fields in MARC (6XX) also support relationship designators. But as there is quite a lot of new work taking place with regards to subjects in RDA at the moment, we have decided to delay adding support for subject relationships to MARC Report until a later version. | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ==== Local Terms ==== | ||
+ | |||
+ | In RDA, the relationship designators listed in Appendix I and Appendix J are considered ' | ||
+ | |||
+ | //"If none of the terms listed in this appendix is appropriate or sufficiently specific, use another concise term to indicate the nature of the relationship" | ||
+ | |||
+ | In order to support the concept of an Open list in MARC Report, we have added a separate editors for Local terms to the Appendix I and Appendix J options; these editors are accessed by pressing the 'Local Terms' button at the top right corner of the corresponding appendix options (shown above). | ||
+ | |||
+ | Pressing this button displays the form shown here: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Use this form to add a term for a relationship that is not already listed in Appendix I or Appendix J. | ||
+ | |||
+ | Note that terms added to this list are not displayed in the list of official RDA terms for the corresponding appendix. However, if the option to ' | ||
+ | |||
+ | The caption ' | ||
+ | |||
+ | {{: | ||
+ | \\ | ||
+ | |||
+ | But this caption is stripped from the data if and when it is added to the MARC record. | ||
+ | |||
+ | If you invest time and thought in creating Local Terms, we recommend that you add your files of local terms to your backup regimen. The names for these files are: | ||
+ | |||
+ | My Documents\MarcReport\Options\local.rdi | ||
+ | My Documents\MarcReport\Options\local.rdj | ||
+ | | ||
+ | (where the last letter, ' | ||
+ | | ||
+ | The local filename is also listed in the status bar of the 'Edit Local terms' form ((where in fact, clicking on the status bar will open Explorer into the appropriate folder)) | ||
+ | | ||
+ | |||
+ | ===== Cataloging checks and Validation ===== | ||
+ | |||
+ | When MARC Report checks the relationship designators present in the MARC fields and subfields listed in the table [[244: | ||
+ | |||
+ | The brief message will state, for example: | ||
+ | |||
+ | < | ||
+ | |||
+ | The decision to use ' | ||
+ | < | ||
+ | $e - Relator term | ||
+ | | ||
+ | Designation of function that describes the relationship between a name and a work, | ||
+ | e.g., ed., comp., ill., tr., collector, joint author. </ | ||
+ | |||
+ | Hence our decision to dub these ' | ||
+ | |||
+ | In addition to this newly added RDA relationship support in MARC Report, we have also added some new cataloging checks that will help prevent some obvious errors when adding relationship designators to headings fields. | ||
+ | |||
+ | For example, if a subfield $i is added to a 700 field that does not contain a subfield $t, a cataloging check error message like the following will display-- | ||
+ | |||
+ | < | ||
+ | |||
+ | --followed by the explanatory note: | ||
+ | |||
+ | < | ||
+ | relationships between the resource and another work, expression, manifestation, | ||
+ | but this field lacks the content designator necessary (subfield $t, Title of a work) | ||
+ | for a work, etc. Remove the subfield $i, or update the 7XX to describe a related work, etc. | ||
+ | </ | ||
+ | |||
+ | Similarly, if a subfield $e is added to a 700 tag that contains a subfield $t a cataloging check error message and explanatory note will also be displayed: | ||
+ | |||
+ | < | ||
+ | |||
+ | < | ||
+ | This heading refers to another resource, and not to a person, family, or corporate body | ||
+ | associated with the resource: thus, subfield $e (Relator term) cannot be added to field. | ||
+ | Delete the $e from this 7XX. | ||
+ | </ | ||
+ | |||
+ | ===== Updates ===== | ||
+ | |||
+ | MARC Report supports automatic updates to the lists of relationship designators that it uses. | ||
+ | \\ | ||
+ | For a complete description of how it works, please [[245: | ||
+ | \\ | ||
+ | To view the RDA relationship designator update history, click 'List Updates' | ||
+ | |||
+ | |||