BIBCO colleagues, please see forwarded message below about OCLC Connexion functionality change. -- Jessalyn Zoom
From: CONSER Cataloging Discussion List [mailto:[log in to unmask]] On Behalf Of Patton,Glenn
Sent: Wednesday, June 11, 2014 4:50 PM
To: [log in to unmask]
Subject: [CONSRLST] OFFICIAL: Changes to controlling
Posted on behalf of Becky Dean (and posting again since the June 10th posting seems not to have been distributed).
Apologies for duplication; the message below will be cross-posted to various listservs.
Earlier today, changes were made as part of a Connexion install. To take full advantage of these changes, please log off of your current session and establish a new session.
The first of this is that Library of Congress validation records are no longer used for controlling. These are authority records that include the phrase: Record generated for validation purposes. As of June 9, there are 78,903 authority records containing that phrase in a 667 note. If a heading in a bibliographic record is controlled to one of those headings and the user executes a control all command, the heading will be automatically uncontrolled and then attempt to re-control the heading to non-validation authority record(s). It is not necessary to uncontrol the heading before re-controlling in this scenario—the controlling software will automatically identify a heading associated with a subject validation record, and as part of the control all command will attempt to re-control the heading.
The reason for the change to functionality is to work to eliminate incorrect changes to subdivisions, especially related to $x and $v, respectively. Over many years staff have worked to decrease the incorrect subdivision code flips, and after extensive tracking found that the remaining problems were related to the fundamental goal of controlling a heading to the fullest possible form. Testing found that eliminating subject validation records from controlling allowed the software to find the fullest forms and ensure that subdivision codes were not changed incorrectly.
CHANGES TO EXCLUDE MATCHING TO VALIDATION RECORDS WHEN CONTROLLING There are three scenarios that will result when a heading previously controlled to a validation record is attempted to be recontrolled:
1) There is no change to the text of the heading, but the authority record(s) associated with the controlled heading have changed. In this situation, a message will be presented in Connexion that reads: One or more headings were controlled and linked. This message will be presented when there is no visible change to the text of the controlled headings.
Heading in bibliographic record is controlled to:
650 0 African Americans $v Periodicals (sh2007100332)
Heading in the bibliographic record would be controlled to the following two records as part of the control all command:
650 0 African Americans (sh85001932) $v Periodicals (sh99001647)
2) There is a change to the text of the heading based as a result of not using the subject validation records
Heading in bibliographic record is controlled to:
650 0 Christianity ǂz Africa ǂx History.
Heading in the bibliographic record would be controlled to the following single record as part of the control all command:
650 0 Church history.
3) The prior fully-controlled heading is left as partially controlled because authority records that are not validation records do not exist for the complete heading.
No examples of this type were found during testing.
CHANGES TO DISALLOW CONTROLLING OF SERIES HEADINGS WHEN 008/12 EQUALS C Not allowing controlling of series to 008/12 = c (series-like phrases)
As of June 10, headings in authority records in which 008/12 is equal to ‘c’ will no longer be controllable. The headings will not be automatically removed from all existing bibliographic records with this change. Headings of this type will be automatically uncontrolled as part of a control all command.
CHANGES TO EXCLUDE MATCHING TO BLOCK AUTOMATIC CONTROLLING WHEN 400 IS A NON-QUALFIIED NAME Previously, if an unqualified personal name heading in a bibliographic record were to match to a 400 field, and the 100 field of the heading were qualified then the heading was automatically controlled. That functionality has changed, and regardless of the form of the heading in the 100 field, an unqualified personal name that matches a 400 field will result in the opening of the control headings window and the user will need to take the appropriate action.
Please contact OCLC Customer Support at [log in to unmask] regarding any questions or problems related to these changes in functionality. Reporting problems directly to Customer Support will ensure that your problem will be investigated and tracked for resolution.
In addition, the problem impacting the incorrect landing location when browsing the LC Names authority index will be resolved in the August Connexion install. Thank you for your patience related to this problem.
Senior Product Analyst
6565 Kilgour Place
1-800-848-5878, ext. 5144