Print

Print


Mary Jane,

 

The latest example is a geographic name: Moselle. This, and the corporate bodies that I have seen change, are because (I think) under the guidelines, we are directed to add the date qualifier to the AAP. The personal names are the undifferentiated changes with the qualifiers.

 

Because I deal with a linked authority system, the access points in our catalog are changed to the new form. I have to review the changes and usually change some of them. It causes me great concern about when we will be ready for a “linked system” that doesn’t require this review.

 

THIS OLD PREVIOUSLY MATCHED AUTHORITY RECORD HAS BEEN REPLACED BY THE NEW ONE WHICH FOLLOWS (CHANGES MARKED BY ">>>>>")

REC   940

  (****86)

     (001) FCN    0      A^n  50009537 ^

>>>>>      FIX    0      A^140918n| acannaabn          |a ana |||  00000nz   2200000n  4500^

     (003) CF3    0      A^DLC^

     (005) CF5    0      A^20100511070951.0^

     (010) RCN    0      A^n  50009537^

     (034) CCM    0      D^E0063000^   E^E0063000^   F^N0490000^   G^N0490000^   2^geonames^

     (035) LSN    0      A^(OCoLC)oca00045055^

     (040) ACS    0      A^DLC^   B^eng^   C^DLC^   D^NN^   D^OCoLC^

     (043) GAC    0      A^e-fr---^

>>>>>(151) HEG    0      A^Moselle (France)^

>>>>>(451) FRG    0      W^nnaa^   A^Moselle, France (Dept.)^

>>>>>(551) AFG    0      A^Meurthe-et-Moselle (France)^

>>>>>(551) AFG    1      A^Westmark (Germany)^

     (670) NAF    0      A^Statesman's yrbk. 1923, 1945.^

     (670) NAF    1      A^GeoNames, algorithmically matched, 2009^   B^(adm2; 49degree00'00"N 006degree30'00"E)^

     (781) SLZ    0 [b0] Z^France^   Z^Moselle^

 

 

THIS IS THE NEW AUTHORITY RECORD WHICH REPLACES THE OLD PREVIOUSLY MATCHED ONE SHOWN ABOVE (CHANGES MARKED BY ">>>>>")

REC   940

  (****86)

           FIN    0      A^ ^

     (001) FCN    0      A^n  50009537 ^

 


LIBRARY ID - $MARCIVE        SEPTEMBER 19, 1914      JOB-                 MARCIVE

 

>>>>>      FIX    0      A^800401n| azannaabn          |a ana      02129cz   2200229n  4500^

     (003) CF3    0      A^DLC^

     (005) CF5    0      A^20140909171150.0^

     (010) RCN    0      A^n  50009537^

     (034) CCM    0      D^E0063000^   E^E0063000^   F^N0490000^   G^N0490000^   2^geonames^

     (035) LSN    0      A^(OCoLC)oca00045055^

     (040) ACS    0      A^DLC^   B^eng^   E^rda^   C^DLC^   D^NN^   D^OCoLC^   D^DLC^

     (043) GAC    0      A^e-fr---^

>>>>>(046) SCD    0      S^1790^   T^1871^

>>>>>(151) HEG    0      A^Moselle (France : 1790-1871)^

>>>>>(368) ATC    0      B^Department^

>>>>>(551) AFG    0      A^Moselle (France : 1919-)^

     (670) NAF    0      A^Statesman's yrbk. 1923, 1945.^

     (670) NAF    1      A^GeoNames, algorithmically matched, 2009^   B^(adm2; 49degree00'00"N 006degree30'00"E)^

>>>>>(670) NAF    2      A^Wikipedia, Sept. 5, 2014^   B^(Moselle: department in the east of France named after the river Mosel*

                        *le. It is one of the original 83 departments created during the French Revolution on March 4, 1790. It*

                        * was created from the former province of Lorraine.  After the French defeat in the Franco-Prussian War*

                        * of 1870-1871, almost all of the Moselle department, along with Alsace and portions of the Meurthe and*

                        * Vosges departments, was returned to the German Empire by the Treaty of Frankfurt.  In 1919, with the *

                        *French victory in the First World War, Alsace-Lorraine was returned to France by Germany at the Treaty*

                        * of Versailles. However, it was not decided to recreate the old departments of Meurthe and Moselle by *

                        *reverting to the old department borders of before 1871. Instead, Meurthe-et-Moselle was left untouched*

                        *, and the German Region of Lorraine was reconstituted as the new department of Moselle. Thus, the Mose*

                        *lle department was reborn albiet smaller than before. During Wo…

 

Thanks for asking,

 

Mary Charles

 

 

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Cuneo, Mary Jane
Sent: Thursday, October 02, 2014 5:26 PM
To: [log in to unmask]
Subject: [PCCLIST] Changes to Group 2 NARs (was: Date of expression in DLC authority records?)

 

Mary Charles,

 

Can you say more about the problem you are seeing with personal, corporate and geographic names being changed on bibliographic records?  It may be the result of work being done on NARs for FRBR Group 2 entities as they are encountered and recoded to RDA.  The impact of this is of interest, but it’s probably a different topic from the discussion below (FRBR Group 1 entities/WEMI).

 

Mary Jane Cuneo

Serials cataloging and NACO

Information and Technical Services

Harvard Library

 

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Lasater, Mary Charles
Sent: Thursday, October 02, 2014 9:55 AM
To: [log in to unmask]
Subject: Re: Date of expression in DLC authority records?

 

All,

 

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.

 

Thanks,

 

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.

 

Stephen

 

 

 

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.

 

Bob

 

Robert L. Maxwell
Ancient Languages and Special Collections Cataloger
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 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
<http://www.minitex.umn.edu/>

  "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

Ph: 612-625-2328

Fx: 612-625-3428

ORCID:  0000-0002-3590-1242