Print

Print


Since I've been dragged into the conversation <grin>:  Yes, I've provided automated assistance for this problem in the cataloger's toolkit.  It's available as a sort-of-automatic feature as well as an operator-mediated feature, but I recommend that it only be used under direct operator supervision; certainly, there are too many vagaries in the existing data to leave this to a batch program.  If you're interested in knowing how this works, I've recently roughed out some documentation; this needs to be subdivided into sections but I think that it is at least correct (except for the typos and an uncertainty about what the bold-facing of certain headings means):

                http://files.library.northwestern.edu/public/CatalogersToolkit/Documentation/Online/#multilanguagebutton

Some might be interested in the description of the "libretto" button, which immediately follows the description of the "multi-language" button.

Gary L. Strawn, Authorities Librarian, etc.           Twitter: GaryLStrawn
Northwestern University Library, 1970 Campus Drive, Evanston IL 60208-2300
e-mail: [log in to unmask]   voice: 847/491-2788   fax: 847/491-8306
Forsan et haec olim meminisse iuvabit.       BatchCat version: 2007.25.428

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Amy Turner
Sent: Friday, July 19, 2013 6:17 AM
To: [log in to unmask]
Subject: Re: [PCCLIST] RDA-ifying a $l Language & Language record

I'm the one that suggested that Rich write to the list, and after reflection, I have a proposed answer that I'd like to throw out for comments.   I think we should delete the cross references, since they are appropriate to the combination of the two expressions, not the individual expressions.  At any rate, references are not core under RDA.  I don't think we should edit any already created bibliographic records.   OCLC does not require this, and could do a program that would change all 240's with [language] & [language] to the two appropriate 700/$t's   Hmmm, could that be done in the authority file?   Maybe it is harder than I think, or Gary Strawn would have made it so ...

Amy


Amy Turner

Monographic Cataloger and Authority Control Coordinator
Duke University Libraries

[log in to unmask]


From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Richard Murray
Sent: Thursday, July 18, 2013 1:32 PM
To: [log in to unmask]
Subject: Re: [PCCLIST] RDA-ifying a $l Language & Language record

Thanks, Bob.  Fortunately, the author in question is (thus far, at least) minor, and I can't find any other collections of his poetry in WorldCat, which at least makes that part easier.

Rich


Rich Murray
Metadata Librarian
Catalog Librarian for Spanish & Portuguese Languages
Duke University Libraries
Durham, North Carolina
[log in to unmask]<mailto:[log in to unmask]>



From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Robert Maxwell
Sent: Thursday, July 18, 2013 1:15 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: [PCCLIST] RDA-ifying a $l Language & Language record

This is a little trickier than it seems since it not only involves to expressions, but it involves selections.

A. The Work.

"Selections" denotes a collection, an aggregate work, and it is at the work level. Separate collections are separate works. As you note, the preferred title for this particular kind of collection is "Poems. Selections", and the authorized access point is formed by combining the authorized access point for the creator with the preferred title for the work, "Name. Poems. Selections" (6.27.1.2). However, 6.27.1.9 instructs: "Make additions to access points if needed to distinguish the access point for a work from one that is the same or similar but represents a different work."

If there is only one collection of poems by a particular creator, then the authorized access point "Name. Poems. Selections" does not need to be distinguished from another authorized access point. But if there is more than one collection of poems by the same creator, then the authorized access point "Name. Poems. Selections" is insufficient to distinguish the access point, because the different collections are different works. So under 6.27.1.9 something must be added to the authorized access point for the work.

The new NACO training materials, soon to be posted at the Catalogers Learning Workshop, uses the example of three collections of Dickens's short stories:

Selected short fiction / Charles Dickens ; edited with an introduction and notes by Deborah A. Thomas (Harmondsworth : Penguin, 1976).
The supernatural short stories of Charles Dickens / edited with an introduction by Michael Hayes (London : John Calder ; Dallas : Riverrun Press, 2010).
Christmas stories / Charles Dickens (New York: The University Society, 1908).

Each of these is a totally different collection, with different stories, i.e., each is a different aggregate work. According to 6.27.1.9, form of work, date of the work, place of the work, or something else could be used to distinguish the authorized access points. Since they all have the same form and the same language, those won't work to distinguish them, but "other distinguishing characteristic" or date would. Some possibilities here are:

Use the title of the collection as an "other distinguishing characteristic":
Dickens, Charles, 1812-1870. Short stories. Selections (Selected short stories)
Dickens, Charles, 1812-1870. Short stories. Selections (Supernatural short stories of Charles Dickens)
Dickens, Charles, 1812-1870. Short stories. Selections (Christmas stories)

Use the compiler of the collection as an "other distinguishing characteristic":
Dickens, Charles, 1812-1870. Short stories. Selections (Thomas)
Dickens, Charles, 1812-1870. Short stories. Selections (Hayes)
Dickens, Charles, 1812-1870. Short stories. Selections (University Society)

Use the date of the work:
Dickens, Charles, 1812-1870. Short stories. Selections. 1976
Dickens, Charles, 1812-1870. Short stories. Selections. 2010
Dickens, Charles, 1812-1870. Short stories. Selections. 1908

In my opinion, the date of the work is the least useful if we actually want to help our users find the collection they're looking for, but the decision of which addition best distinguishes between the works is a matter of the cataloger's judgment.

So if there is more than one collection of poems, the authorized access point for each work needs to be distinguished from the others:

Name. $i Poems. $k Selections $s (Other distinguishing characteristic) [assuming that's what you use to distinguish]

B. The Expressions.

Only after you've decided on (and established) the authorized access point for the work can you think about the access points for the two expressions.

There are two options.

1. (followed by LC but not required by PCC):

Use the authorized access point for the work to represent the expression in the original language (in your case, Spanish):

Name. $i Poems. $k Selections $s (Other distinguishing characteristic)

[Note: substituting the work access point for that of the original-language expression is an AACR2 practice]

Create an authorized access point for the translated-language expression:

Name. $i Poems. $k Selections $s (Other distinguishing characteristic). $l French

2. (followed by some PCC libraries, and in keeping with RDA's practice of constructing access points for particular expressions, 6.27.3):

Create an authorized access point for each expression:

Name. $i Poems. $k Selections $s (Other distinguishing characteristic). $l Spanish

Name. $i Poems. $k Selections $s (Other distinguishing characteristic). $l French

In either case further distinguishing might be necessary at the expression level if more than one expression in the same language exists.

Bob

Robert L. Maxwell
Head, Special Collections and Formats Catalog Dept.
6728 Harold B. Lee Library
Brigham Young University
Provo, UT 84602
(801)422-5568

"We should set an example for all the world, rather than confine ourselves to the course which has been heretofore pursued"--Eliza R. Snow, 1842.

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Richard Murray
Sent: Thursday, July 18, 2013 10:35 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: RDA-ifying a $l Language & Language record

Hi all,

We have a question about how to RDA-ify a NAR with "Language A & Language B" in subfield l.  We've read the guidelines and understand them in theory, but this is the first one we've done, so we're having trouble figuring out how it works out in practice.

My AACR2 AR (with the 667 telling me I can't use it under RDA till I fix it) is this type:

100 1  Name. $t Poems. $k Selections. $l French & Spanish
400 1 Name. $t Title from 245

We know we have to create two new ARs and ask LC to delete the old one, but we're unsure about what the two new ones should look like, particularly the 400s, and also what (if any) impact this has on the bib record that this AR was created for.  (We are changing this record not because we are cataloging/recataloging that book, but because we changed the form of the personal name and now are doing the up-the-chain/down-the-chain updating and RDA-ifying).

Is this what our two new ARs should look like?

Record #1:
100 1  Name. $t Poems. $k Selections
400 1  Name. $t Title from 245

Record #2:
100 1  Name. $t Poems. $k Selections. $l French
400 1  Name. $t Title from 245

So that both 400s go back to the same title (which was the parallel edition)?  Or are those 400s unnecessary?  Do we need records with 100s and no 400s?

Meanwhile, do we have to go back to the bib record for the piece the AR was created for in the first place and change the access points so they are backed by the new ARs we have just created?

Thanks for any help/guidance.

Rich


Rich Murray
Metadata Librarian
Catalog Librarian for Spanish & Portuguese Languages
Duke University Libraries
Durham, North Carolina
[log in to unmask]<mailto:[log in to unmask]>