Returning to a point made earlier in this discussion and in the PCC task group on AAPs for expressions report, bottom of page 5, the crux of the question is whether an AAP of the form

[Name]. $t [Title.] $l English. $s (Translator name)

implicitly authorizes a bib heading in the form

[Name]. $t [Title.] $l English.

If it does, then LC following its rule of practice at LC/PCC-PS 6.27.3 can use the latter form when only the former is established. If not, then LC will have split files, an obligation to create additional generic authorities, and lots of recataloging to do.  For example, see the authorities under Euripides.  All the AAPs beginning "Euripides. $t Alcestis. $l English" now also include a $s subfield naming a specific translator. A browse "title begins" search in LC's catalog for "alcestis english" finds multiple translations, some by the translators named in the authorities, some by other translators, none with a $s. 

The acceptance of implicitly authorized AAPs for works has a long history. Cf. the task group report, page 6: "A collective expression record as such may be more analogous to the parent work, in
that it does not need to be established in the authority file but can still collocate along with differentiated expressions, as long as the base title is the same."  What's needed is clarification from LC about whether generic expression AAPs on bib records can be considered implicitly authorized, and consensus that in the case of translations, the same resource can have two forms of authorized access, one generic and one more specified, and that which one to use is a catalog-level decision.

That said, it should also be noted that LC bib records which remove specificity from an expression AAP should not overlay OCLC records with greater specificity for the same expression.

Alternatively, there could be a decision to abandon generic expression AAPs and generate lots more work for everybody (think deck chairs, Titanic ...).


On Thu, Oct 2, 2014 at 4:31 PM, Wilson, Pete <[log in to unmask]> wrote:

I would love to see these questions sorted out.  I find the current situation regarding generic vs. specific expression AAPs very confusing, and I think conventions need to be put in place to reduce the uncertainty and ambiguity.


Pete Wilson

Vanderbilt University


From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Lasater, Mary Charles
Sent: Thursday, October 02, 2014 8:55 AM

To: [log in to unmask]
Subject: Re: [PCCLIST] Date of expression in DLC authority records?




I am very glad to see this discussion and suggestions for practical ways to handle these with authority records.  Stephen’s suggestion makes a lot of sense and should avoid the problem I am seeing with personal, corporate and geographic names in bibliographic record access points being changed inappropriately by linked authority records.




Mary Charles Lasater


From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Stephen Hearn
Sent: Thursday, October 02, 2014 8:43 AM
To: [log in to unmask]
Subject: Re: [PCCLIST] Date of expression in DLC authority records?


Bob's case against using dates in generic (or "generic") expression authorities makes sense, too, and agrees with the recommendation of the PCC Access Points for Expressions Task Group. There's still an ambiguity, though--when the title looks generic and the 046 contains a specific date, which data element determines the AAP's intended scope? Does the AAP look generic? Page 9 of the task group report comments, "Usually, then, these special fields [e.g., 046] would only apply when those same elements are also included as additions to the access point."  So maybe these are cases where the 046 was applied in error and the generic intent of the record is more evident from the AAP.


In practical terms, given that the authorities have been posted for some time and may have been used to control bib AAPs, I'd be reluctant to resolve the ambiguity in the authorities by adding a date (per the task group recommendation) to the AAP, since the unspecified AAP form may have been used generically to control other expressions.  It would be safer to remove the 046, let the existing authority stand as generic, and create a new authority with more thorough specificity if needed.






On Wed, Oct 1, 2014 at 1:56 PM, Robert Maxwell <[log in to unmask]> wrote:

The presence of a recorded date of expression means the record is no longer a “generic” record covering all English language expressions of a given work. The record applies only to the expression that was created in that year (or first published in that year). Different expressions are created in different years, so by recording a specific year you are pinning the record down to a specific expression.


Bizarrely, there is no evidence for the 046 date 1927 in n  85022980, but it does appear from an OCLC search that an English language expression of Rølvaag’s I de dage was indeed published in 1927, so this record would correspond to that particular expression, not another (perhaps there is only one English language expression of this work, but if there are more than one, n  85022980 can only apply to the expression first created in 1927).


Randomly looking at a few of the other examples you give, most of them don’t seem to have any evidence for the 046 field data either.


In my opinion if any expression-related attribute aside from language (377) is recorded in an authority record, that takes the record out of the realm of “generic” language expression and it becomes a record for a specific expression, the one that corresponds to whatever attributes have been recorded (in these cases, date of first creation of the expression). So my response to Mark’s question would be “No, these records should not be treated as describing a generic expression, they describe a specific expression.” But I have no idea what the LC catalogers were thinking when they enhanced these records with 046 fields.




Robert L. Maxwell
Ancient Languages and Special Collections Cataloger
6728 Harold B. Lee Library
Brigham Young University
Provo, UT 84602

"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 Mark K. Ehlert
Sent: Wednesday, October 01, 2014 9:59 AM
To: [log in to unmask]
Subject: Date of expression in DLC authority records?


I've come across several authority records exclusively sourced and edited by DLC (per the 040 field) for English translations that include 046 dates that specify the date of expression.  The heading itself is generic following LC-PCC PS 6.27.3--Name. Title. English--but the record is made specific with that added date.  Many, but not all, of the records were last edited in February-March 2013, which point to the Phase 2 RDA Authorities project.  However, none of the 1xx/4xx headings use the $f, which I presume would be the source for the automated population of the 046 field.  Several 046s also don't match the source dates in the 670s; manual intervention is implied there.


Random examples by LCCN:
n  90636367
no 97019257
n  80148532
n 2012079161
n 2013001274
n 2013037659
n 2013062190

So a question of practice for those of us who aren't LC: Should these records be treated as generic expression?  Or specific expression?  I presume the 046s aren't meant to act as the start date(!) for a collection of English expressions covered by a single record.  I have one translation record in front of me I'd like to edit, but don't know how to go about enhancing it, if at all (n  85022980, last touched in September 2013).


Mark K. Ehlert                 Minitex
Coordinator                    University of Minnesota
Digitization, Cataloging &     15 Andersen Library
  Metadata Education (DCME)    222 21st Avenue South
Phone: 612-624-0805            Minneapolis, MN 55455-0439

  "Experience is by industry achieved // And perfected by
the swift course of time." -- Shakespeare, "Two Gentlemen

of Verona," Act I, scene iii




Stephen Hearn, Metadata Strategist

Data Management & Access, University Libraries

University of Minnesota

160 Wilson Library

309 19th Avenue South

Minneapolis, MN 55455

ORCID:  0000-0002-3590-1242

Stephen Hearn, Metadata Strategist
Data Management & Access, University Libraries
University of Minnesota
160 Wilson Library
309 19th Avenue South
Minneapolis, MN 55455
Ph: 612-625-2328
Fx: 612-625-3428
ORCID:  0000-0002-3590-1242