Differences

This shows you the differences between two versions of the page.

Link to this comparison view

phelp:helprdaoptions [2017/12/01 18:31] (current)
Line 1: Line 1:
 +RDA Options
 +
 + 
 +RDA RELATIONSHIPS
 +
 +Because of the complexity of this topic, detailed help on the functionality of the RDA Relationship support is available online only: 
 +
 +http://www.marcofquality.com/wiki/mrt/doku.php?id=help:rdarelationships
 +
 +Brief help on this section follows.
 +
 +ENABLE RDA RELATIONSHIP SUPPORT
 +
 +To disable RDA Relationship support completely, uncheck the option on the top-left of this page.
 +
 +RDA APPENDIX I and J
 +
 +On the left side of the page are two groups of MARC tags and subfields for RDA Relationships: one for RDA Appendix I and one for Appendix J.
 +
 +Use the checkbox for a MARC tag/subfield code (e.g., 100e) to enable/disable validation checks and pop-up lists for the corresponding tag/subfield). These options apply both to editing and validation.
 +
 +For example, in the Appendix I group, if '100e' is selected, then in MARC Report:
 +
 +    Text in 100 subfield $e will be validated against terms from RDA Appendix I
 +    Pressing <F7> while editing subfield $e provides a pop-up list of RDA Appendix I terms
 +
 +On the other hand, if '100e' is not selected, then in MARC Report:
 +
 +    Text in 100 subfield $e is not validated
 +    Pressing <F7> while editing subfield $e in tag 100 has no effect
 +
 +Thus, these options apply both to editing __and__ validation (the latter includes both record mode and batch mode).
 +
 +
 +FORCE CASE-SENSITIVE VALIDATION
 +
 +Because RDA is not particularly concerned with capitalization, the default is false ('off') for this option--capitalization differences will not generate a warning message. 
 +
 +However, you could turn this validation check on if you are concerned about consistency in the display of the relationship terms in your online catalog (especially those from Appendix J, perhaps).
 +
 +SHOW REMINDER IF MISSING RELATIONSHIPS
 +
 +This option will display a message if the record is following RDA description conventions (040 $e is 'rda') and a  heading is missing an RDA relationship (for example, a bib 700 field without $e). The default is true. 
 +
 +Why? In RDA it is very important to specify the relationship between an Agent and a Resourceľthis will make your data more useful, especially if that data is to function well in the world to come after MARC. 
 +
 +REQUIRE COLON AFTER SUBFIELD $i
 +
 +This option is true by default. If selected it:
 +
 +    1. adds a colon after a selected relationship designator, added in subfield $i
 +    2. warns about a missing colon in an existing subfield $i
 +
 +If you are not using a colon as separating punctuation for this data, despite LCPCC-PS 1.7.2, then turn this option off. (Note that no warning is given when this option is turned off and a term in subfield $i ends in a colon).
 +
 +CAPITALIZE $i PHRASE
 +
 +This option is false ('off') by default. If selected, when a phrase from Appendix J is added to a 7XX field, the first letter of the phrase will be capitalized.
 +
 +Since these phrases might display at the beginning of the relationship in the catalog, some users may want them to begin with an uppercase letter. 
 +
 +A NOTE ABOUT THE SCOPE OF THE ABOVE OPTIONS
 +
 +The two options common to both Appendix I and Appendix J ('force case-sensitive validation' and 'show reminder if missing') are applied only to the tags that are selected in the boxes above them. For example, consider:
 +
 +  100 $aDoe, John,$eAuthor.
 +  
 +If '100e' is selected, and the Appendix I option 'Force case-sensitive validation' is selected, then a message will display about the term $e being in the wrong case (it should be 'author', not 'Author'). If '100e' is not selected, no message will be shown (since in that case, the 100 $e will not even be validated).
 +
 +The two options that appear only in the Appendix J section ('require colon after $i' and 'capitalize $i phrase') are 'global'--they apply to any of the tags in the Appendix J box, whether they are selected or not.
 +
 +
 +RDA RELATIONSHIP EDITORS
 +
 +At the top of the right side of the RDA options page, are the 'Relationship editors' for RDA Appendix I and RDA Appendix J.  These editors provide 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.
 +
 +These editors use the 'Sets' design that can be found throughout MARC Report: we supply a default set of options, which the user may then customize by deriving their own 'set' from the default.
 +
 +Press 'Edit' to open the editor. The default 'matrix' will be displayed. Each RDA term from the associated Appendix will be listed on the left, followed by a series of checkboxes. 
 +
 +For details on how to customize these matrices, please visit the online help cited at the top of this page.
 +
 +RDA  AUTOMATION FOR 336/337/338
 +
 +The 'F10' macro, added in version 242, makes it easy to add RDA tags 336, 337, and 338 to records that you are hybridizing (by hybridizing we mean AACR records that are being manually upgraded to conform to RDA/MARC).
 +
 +The first group tells the program what subfields you want to add to the 336, 337, and 338 when F10 is pressed. You may check both $a and $b, $a only (for just the RDA Term), or $b only (for just the MARC Code for the term). 
 +
 +If both subfields are unchecked, the program will not attempt to add any fields when F10 is pressed. 
 +
 +By default, subfield $a is checked and subfield $b is not.
 +
 +These options are also used to determine which data appears in the dropdown lists, which are described in detail in the section that follows.
 +
 +There is no option to supply the $2 subfield because the program will automatically add 
 +
 +  336 ... $2rdacontent
 +  337 ... $2rdamedia
 +  338 ... $2rdacarrier
 +  
 +as appropriate, to the end of each tag that it adds. Note, however, that pressing F10 in a record that already contain any 33X tags will not add missing $2's to these tags.
 +
 +The second option tells the program to **Delete existing 336, 337, and 338 tags** whenever F10 is pressed. This might be useful if you are running the hybridizer to correct these tags in a batch of records. 
 +
 +Note: If the record in question already contains any of the 33X Tags, and the 'Delete existing ...' option is not selected, the hybridizer will not run.
 +
 +CUSTOMIZE AUTOMATION BEAHVIOR
 +
 +Click on this button to display a small form that allows you to configure hybridization in more detail.
 +
 +Fallback Option
 +
 +The first tab in this section tells the program what to do when the hybridizer is unable to automatically determine values for all three  RDA fields. 
 +
 +The fallback options are:
 +    On any fail, undo all changes
 +    On any fail, add empty templates for unfilled tags
 +    On any fail, add my default values to each tag
 +    On any fail, add my default values to unfilled tags
 +    On any fail, keep whatever changes were made
 +
 +NB. Not all of these options may be immediately visible; use the scroll bar on the right to view all of the options.
 +
 +Notes
 +
 +By 'empty templates' we mean that the program will add a subfield $a or $b without any data to the tag. So if the program was unable to determine a value for Media Type, and this option was selected, the resulting 337 would look like this:
 +  337   $a $2rdamedia
 +Then, one may simply click on the 337 and select the wanted Media type from the dropdown list, or type it in yourself. (MARC Report will of course prompt you with an error message about the empty subfield $a).
 +
 +The 'default values' are something you can setup yourself for each of 336, 337 and 338. To access these options click on the 'Default values' tab at the top of the form.
 +
 +The default 'default values' are:
 +  336   $atext $2rdacontent
 +  337   $aunmediated $2rdamedia
 +  338   $avolume $2rdacarrier
 +
 +If running the hybridizer in batch mode on a file of records, do not select either of the options that 'add empty templates'. This will generate an error message.
 +
 +The choice of a default for an Edit Session may well differ from the choice of a default from batch mode. For example, in batch mode you may want to select 'On any fail, do not try to fill unfilled tags' so that the program will populate all of the fields it is confident about, and not try to do anything else. Whereas in edit mode, you may want to add 'templates' for the unfilled values to prompt you to fill them.
 +
 +The batch mode version of the hybridizer (available under the Utilties menu) defaults to the options as setup in the RDA page of the program options. But it presents a copy of this options form, so that you can tweak the options for a batch run before starting it. 
 +
 +
 +===== Editing 336, 337, 338 =====
 +
 +When you are editing a record that has 33X tags, click on the data column of one of these fields to automatically display a list of all valid RDA terms and codes for that tag.
 +
 +The listbox is shaded slightly to set it apart from the other data in the record. The list is sorted in alphabetical order, with a caption in brackets at the top.
 +
 +Note: Selecting ths caption in brackets does not add to or change the field contents. 
 +
 +To scroll through the list, grab the slider on the right side of the screen with your mouse and move it up or down (alternately, use the up and down arrow keys to scroll through the list):
 +
 +To select an entry from the dropdown list, click on it with your mouse; if you are instead using the arrow keys to navigate the list, just press <Enter>.
 +
 +Note that the first subfield is not displayed in the list (this is true even if 'Add $a' is not enabled in the options); the program will add the leading subfield as soon as a selection is made from the list. 
 +
 +The purpose of this omission is to make type-ahead (aka incremental search) possible. For example, if editing an empty 336 field is empty, simply typing 't' will:
 +  - open the dropdown list
 +  - jump to the first entry beginning with a 't', then
 +  - select that entry
 +  
 +At this point, one may simply press <Enter> to add the selection to the field and close the dropdown list, or continue typing until the desired list value is selected. If we quickly type an 'e' after the 't' then the 'text' content type will be selected in the list, etc. 
 +
 +To edit the actual field contents by hand, simply click on the field a second time:
 +
 +The second click will close the dropdown list and make it possible to edit the field manually. However, the list is still lurking in the background and may be re-activated at any time by pressing the down-arrow button on the right side of the screen (or alternately, by pressing the down arrow key).
 + 
 +
 +
  
phelp/helprdaoptions.txt ┬Ě Last modified: 2017/12/01 18:31 (external edit)
Back to top
CC Attribution-Noncommercial-Share Alike 3.0 Unported
Driven by DokuWiki Recent changes RSS feed