Earlier this year OCLC changed the location for retrieving and downloading software, including Connexion Client.  The new site is Software & Reports.  The Product Services Web page (PSWeb) is now discontinued.

Northern Illinois librarians, for this and other updated information on online cataloging resources, consider attending next month’s LACONI Technical Services Section program (see Joy’s post below).


Hello everyone!

It’s been awhile since we have posted anything new, but that may change. Richard and I (Joy) will be part of a LACONI Technical Services program on November 10, 2017 at the Tinley Park Public Library in Tinley Park, Illinois, where we will be discussing resources for catalogers. All are welcome to attend.

Registration information is here and on the LACONI website.



ALA’s ALCTS (Association for Library Collections & Technical Services) has been presenting and publishing RDA webinars since 2010.  You can register for live upcoming presentations (this also gives you unlimited access to the recorded webinar); buy recordings up to two weeks after the live event; or wait six months until the recorded presentation is made available without charge.  These webinars can be invaluable for initial training, for learning how to apply RDA in a new context, or for a refresher.

Upcoming webinars are listed here:


Cataloging and RDA webinars, specifically, here:


And free RDA webinars can be accessed here:

If you’re curious about ALCT’s other webinars, check out their general playlist on YouTube:


From a notice posted on OCLC-CAT by Anna Sylvester, OCLC Product Analyst:

Connexion client version 2.63 is now available for download from the Software Downloads area of OCLC’s Product Services web site. Please be aware that:


  • You will be required to upgrade to version 2.63 by 28 February 2017
  • An upgrade warning message will begin appearing when you start Connexion client 2.50 or 2.51 beginning in early January 2017
  • We recommend that you review the upgrade instructions before installing Connexion client 2.63
  • To help prevent installation problems with Windows Vista, 7, 8/8.1 and 10, please right-click the file you downloaded and click Run as Administrator


Getting ready for Unicode

 This release of Connexion client 2.63 is part of a group of changes that OCLC is making to expand WorldCat support for full Unicode characters and scripts to better represent your international collections. When complete, WorldCat will expand support from 15 scripts to all scripts that are represented in Unicode.


This means that by the end of 2016, WorldCat users will have the ability to:


  • Catalog using full Unicode (available now in Connexion client 2.63)
  • Upload records with full Unicode
  • Search across full Unicode


As you catalog using Connexion client 2.63 please be aware that:


  • WorldCat now supports all Unicode characters. OCLC has removed all limitations on MARC-8 and selected non-MARC-8 scripts. If you rely on validation to block unsupported characters, you may need to update impacted workflows.
  • Connexion client 2.63 supports all Unicode characters through version 8.0.0 of Unicode.
  • You can use previously unsupported characters to add new bibliographic records to WorldCat, replace records in WorldCat, import records into the client and export records from the client. All other functions for bibliographic records support these characters as well.
  • You will not be able to use the newly supported characters to search WorldCat until later in 2016. OCLC will announce when searching for the new characters in WorldCat is ready to use.
  • Authority records continue to be limited to the MARC-8 character set.
  • You have a choice to export bibliographic records in MARC-8 (the default) or in UTF-8. If non-MARC-8 scripts are exported in MARC-8 data format, the non-MARC-8 characters are saved in Numeric Character Reference (NCR) format.
  • Valid Unicode characters can appear as empty boxes if they are not supported in your default font.
  • The Arial Unicode MS font that OCLC recommends will not support all scripts. You will have to search for fonts to cover some of the new scripts OCLC supports. Fonts that support these scripts vary in their ability to display characters outside of the script they were designed to support. You may have to experiment to see which font works best for your needs for a particular script. The font selected as the default in the client is applied to the entire record. You may have to move between two fonts to see all of the characters in a record.


If you need assistance installing the Connexion client, please contact an OCLC support office.  

If you create or edit authority records, you should be aware that RDA no longer incorporates the terms “male,” “female,” and “not known” for gender, and that PCC policy is now to use terms from LCDGT (Library of Congress Demographic Group Categories Term and Code List) in field 375 ($2 lcdgt).

You can access LCDGT from ClassWeb.  If you do not have ClassWeb access, you can retrieve a PDF document from the Acquisitions and Bibliographic Access Directorate home page, though it will be slightly less current.  Netanel Ganin of Brandeis University has also posted the terms in a more navigable page in the style of ClassWeb, and he plans to keep his list up to date with each update.

The terms in LCDGT can potentially be used in any setting where you need controlled, single-facet vocabulary for age, educational level, ethnic or cultural identification, gender, language, medical or psychological condition or disability, national or regional affiliation, occupation or field of activity, religion, sexual orientation, or other social group identification; so we may have occasion to refer to it in the future even if we are not assigning gender designations in authority records.

(Gender in authority records and in RDA will be discussed in a little more depth in a forthcoming post on Flaming Catheads.)

Catalogers working with music materials will want to be current with the Music Library Association’s Best Practices for Music Cataloging Using RDA and MARC21. Since February of last year, this document has been integrated with the RDA Toolkit (under the Resources tab).  You need not be logged on to the Toolkit to access Best Practices, but the links to RDA instructions will not work unless you are.

If you want to consult a more traditionally formatted document, the old website of the former Bibliographic Control Committee of the Music Library Association has links to PDF files of Version 1.1 (the final version issued as a complete stand-alone PDF file), a list of changes between versions 1.01 and 1.1, and Supplements to Best Practices for Music Cataloging Using RDA and MARC21, version 1.5, 12 April 2016 (this last document is also available at the current website of MLA’s Cataloging and Metadata Committee).  Be aware, of course, that the Toolkit-integrated document will presumably be more up to date.

Announced on the RSC website:

The RDA full record examples on the Toolkit website have been revised. The examples show authority and bibliographic records in both an RDA element view and a MARC encoding view of the record.

There are also two examples showing diagrams of specific RDA entities, elements, and relationships. More will be added later.

That examples page also includes a link to rball versions of some of the bibliographic examples; they are available in both RIMMF native RDA format and RDF linked data format.

These examples may be accessed from the RDA Toolkit website (http://www.rdatoolkit.org/examples/MARC) or from the link on the Tools tab in RDA Toolkit (http://access.rdatoolkit.org/).

The examples are freely available to all. No subscription to RDA Toolkit is required to access and download the examples.

Posted:23 May 2016