Hi, the question at our end came up: why bother changing at all?
it’s not one of the changes that OCLC recommends if a non-RDA record is hybridized, at least the last checked. The thinking is that general principle was “don’t mess with the transcription fields”
Éva
From: bslwac-bounces@mailman.xmission.com [mailto:bslwac-bounces@mailman.xmission.com]
On Behalf Of Nate Cothran
Sent: Wednesday, April 30, 2014 11:05 AM
To: Backstage Library Works Authority Contol Listserv
Subject: Re: [BSLWAC] Backstage - [et al.] to [and others]
Thanks, Doug. I think it also makes sense to default to [and others] for English-language cataloged records.
I do wonder about deferring to 040 $b in all instances, though. For example, I checked 1,000 records from a sample file we recently processed. Out of those 1,000 records there are 14 records which contain 040
$b. Every instance of the 040 $b is “eng”. However, 12 of the 14 records (86%) are CJK. Granted, none of these records has “[et al.]” in the 245 field. But if they did, would it look out of place to have “[and others]” in there? Possibly no more than having
“[et al.]” in there in the first place, though we could potentially change it to whatever the equivalent for that is in CJK languages.
Here is one more example (from the same sample):
Original Record
008 lang code = ‘ger’
040 $b does not exist in record
245 $a Die Flache :$b Entwurfe fur decorative Malerei, Placate, Buch und Druck … /$c herausgegeben von Felician Baron Myrbach … [et al.].
Processed Record
245 $a Die Flache :$b Entwurfe fur decorative Malerei, Placate, Buch und Druck … /$c herausgegeben von Felician Baron Myrbach [and others].
-Nate
From:
bslwac-bounces+nate=bslw.com@mailman.xmission.com [mailto:bslwac-bounces+nate=bslw.com@mailman.xmission.com]
On Behalf Of Doug Kariel
Sent: Tuesday, April 29, 2014 4:24 PM
To: Backstage Library Works Authority Contol Listserv
Subject: Re: [BSLWAC] Backstage - [et al.] to [and others]
Hi Nate,
I would prefer the [and others] as we catalog in English (040$beng) so our users would expect to see most information in the record in English.
Maybe it should agree with the language in the 040 $b
Regards,
Doug.
Doug Kariel
Head, Technical Services and Systems
Athabasca University Library
1 University Dr.
Athabasca, AB. T9S 3A3
http://library.athabascau.ca
e-mail: dougk@athabascau.ca
Phone: 780-675-6261 Toll free 800-788-9041, ext. 6261
----- "Nate Cothran" <nate@bslw.com> wrote:
> From: "Nate Cothran" <nate@bslw.com>
> To: "Backstage Library Works Authority Contol Listserv" <bslwac@mailman.xmission.com>
> Sent: Tuesday, April 29, 2014 12:26:59 PM GMT -07:00 US/Canada Mountain
> Subject: [BSLWAC] Backstage - [et al.] to [and others]
>
>
>
Currently, we are changing [et al.] (and a very small permutations of this) to
[and others] (BSLW Wiki:
link). This change happens for all languages. So if a record is in English, it is updated to [and others]; if a record is in German it is updated to [and others].
We are also working on a report that lets you know when we change [et al.] to [and others] and the language code (008[35-37]) is not ‘eng’ (i.e. English).
But we wanted to check with you all about whether it made sense to change [et al.] to the foreign-language equivalent of [and others], based on the 008[35-37] language code.
For example, if 008[35-37] is ‘ger’ (i.e. German), would you want us to change
[et al.] to [und andere]? Or we should we continue changing it to
[and others]? Please note that this change only happens for clients that have instructed us to do so via RDA 4.1 (online profile).
Thank you for any thoughts you may have on this question.
![]()

> Nate Cothran | Vice President, Automation Services
Backstage Library Works | Provo, Utah & Bethlehem, Pennsylvania
801.342.5697 |
nate@bslw.com | bslw.com |
ac.bslw.com/mars
> _______________________________________________ BSLWAC mailing list
BSLWAC@mailman.xmission.com
http://mailman.xmission.com/cgi-bin/mailman/listinfo/bslwac
This communication is intended for the use of the recipient to whom it is addressed, and may contain confidential, personal, and or privileged information. Please contact
us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communications received in error, or subsequent reply, should be deleted or destroyed.