Print

Print


Karen

The last time I enquired of LC, there was still no firm date for Phase 3B (I was a member of the working group that wrote and tested the specification).

Concerning ISNIs, it ought to be noted that when the bulk load is done as part of Phase 3B, from a list of correspondences that OCLC will supply, any existing 024 content that has “$2 isni”, and is not on the list, will be removed by the program. There is, therefore, no point in anyone adding an ISNI manually.


Regards
Richard

________________________
Richard Moore
Authority Control Team Manager
The British Library

Tel.: +44 (0)1937 546104
E-mail: [log in to unmask]<mailto:[log in to unmask]>



From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Karen Jensen
Sent: 11 April 2017 16:25
To: [log in to unmask]
Subject: Re: [PCCLIST] RDA metadata fields in name authority records--best practices

Is there any news on when RDA authorities update Phase 3b will take place?

Maybe changing all the 375s that are male and female could also be updated then in batch.

Are others adding ISNIs one by one or waiting for the batch update of Phase 3b?

We've been trying not to make a lot of small updates so as to cut down on the work of reloading authority records, but maybe we should just go ahead with small updates, especially for our own professors.

Karen Jensen
Concordia University

Sent from my iPhone

On Apr 11, 2017, at 10:05 AM, Adam L. Schiff <[log in to unmask]<mailto:[log in to unmask]>> wrote:

The PCC Ad Hoc Task Group on Recording Gender in Name Authority Records has recommended using a subset of the gender terms from LCDGT.  Males and Females are in that subset, but Men, Women, Boys, and Girls are not.  If I encounter a record that has Men or Women I either replace it with Males or Females or delete it if both are present.



The report is available at https://www.loc.gov/aba/pcc/documents/Gender_375%20field_RecommendationReport.pdf
Report of the PCC Ad Hoc Task Group on Gender in Name ...<https://www.loc.gov/aba/pcc/documents/Gender_375%20field_RecommendationReport.pdf>
www.loc.gov<http://www.loc.gov>
Report of the PCC Ad Hoc Task Group on Gender in Name Authority Records October 4, 2016 Authors: Amber Billey, [log in to unmask]<mailto:[log in to unmask]> Matthew Haugen, matthew.haugen@ ...

Hopefully, the revised DCM Z1 375 field will be available soon to put these recommendations into PCC policy documentation.



Adam Schiff

________________________________
From: Program for Cooperative Cataloging <[log in to unmask]<mailto:[log in to unmask]>> on behalf of Lasater, Mary Charles <[log in to unmask]<mailto:[log in to unmask]>>
Sent: Tuesday, April 11, 2017 6:02:43 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: RDA metadata fields in name authority records--best practices

Amy,

Thanks so much for putting this together. I find it very useful.

One of the things I do each month is to ‘check’ a load of authority records that includes many created by catalogers at Vanderbilt. Today I ran into the use of the term “Men” instead of “Males” as  $2 lcdgt

Class web shows both terms in lcdgt. Are both valid for the authority record field 375?

Any advice on what should be the ‘best practice’?

Mary Charles Lasater

From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Amy Turner
Sent: Sunday, April 9, 2017 10:53 AM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: [PCCLIST] RDA metadata fields in name authority records--best practices

Reading the definition of “best practice” in Wikipedia, I see that different best practices are applicable to different institutions.  A wide variety of best practices for the optional RDA fields have already been developed, both formally and informally.   I would like to summarize three levels.


1.      Minimalist.  The fields are optional, with the possible exception of the 046.  (The date is a core element for personal names, and the current NACO training materials state that the 046 is required, but since RDA is not written in terms of tags, one could argue that the date in the 1XX and/or 670 would meet the core requirement).  A strict minimalist approach would forbid use of the fields, to save time in both cataloging and training, and be done with it.  At Duke, we are a little removed from this.  We say that the fields will not be covered in training, but catalogers independent in NACO may use them.  This is a fuzzy line, because the fields are actually emphasized in the latest version of the training materials.  But I, as NACO coordinator and trainer, use only the 046 and do not train in any of the others.   As Mary Charles Lasater pointed out, the new fields can significantly increase training time for NACO, which was already substantial.

2.      Moderate.  This is well described in the British Library Guide to Name Authority Records

(https://www.bl.uk/bibliographic/pdfs/british_library_guide_to_name_authority_records.pdf).



To quote:


        Guideline on Research
BL practice: balance must be struck between fullness and efficiency, when deciding what to record at the element level. Record only those elements that are:
    Readily ascertainable
    Useful
    Expedient to record
Readily ascertainable: only do the amount of research needed to identify the entity, and to create and justify unique authorised and variant access points. Only include in 046/3XX fields appropriate data that has been discovered in the course of this research. Do not do extra research in order to complete additional 046/3XX fields.
Useful: be selective in recording data in 046/3XX fields. For example, only record significant dates in 3XX |s and |t. In 373, only record institutions with which a person has a significant connection. In 372 and 374, only record significant fields of activity and occupations. Any of these fields may be omitted if useful data is not readily ascertainable.
Expedient to record: only search the LCSH file briefly, for suitable terms. If a specific term is not available, use a broader term. If no term is readily ascertainable in a quick search, omit the field. Make full use of Aleph short keys and drop down menus to insert elements into the authority record.


3.      The sky’s the limit.  I have a couple of examples of ARs with optional fields that go beyond the purposes of authority control as outlined by Richard Moore when he started this thread: n 2010043877 and no2011152077.

Discussion thus far indicates that which level a library chooses must be more an attempt to forecast the future than a reflection of current needs.  Of course, the amount of resources available also comes into play.  This is the main reason that Duke has taken the minimalist approach.










From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Michael Colby
Sent: Thursday, April 06, 2017 2:08 PM
To: [log in to unmask]<mailto:[log in to unmask]>
Subject: Re: [PCCLIST] RDA metadata fields in name authority records


Mary Charles Lasater mentions:



"A few ‘best practices’ might be useful.  "



With which I wholeheartedly agree.



Locally, I have established a few "best practices."  For example, we put extra effort into authority records for certain categories, such as entities affiliated with the University and special collections. Hence, I would include our institution in a 373 field for faculty authors. We have a special collection of women composers, so I include a 374 field for them, in the hope that someday (soon?) this field will enrich searching.



But, of course, more widely agreed upon best practices would make a lot more sense. We are all about cooperation, aren't we?



Regards,


Michael Colby
Principal Cataloger
The Library
University of California, Davis
[log in to unmask]<mailto:[log in to unmask]>

[https://outlook.office.com/owa/service.svc/s/GetFileAttachment?id=AAMkAGY4Y2Y4ZDAwLWIzNzYtNGQ4NS04ODQ1LWQ2ODMwNDZiY2RmNgBGAAAAAADTmdznk5ZnSqG3ZBEMeLhZBwBQ0GBopOvSQaXZvL7e6XhQAAAA3ZyPAAAyCGhg0SCtS6tJcs0RKWpdAAKjUG8yAAABEgAQABA81I4JJeJEmpiAMDnJL8g%3D&X-OWA-CANARY=N7c9yDXWMUC7J3dCdaNqzDCEZaQXfdQYKdGPtfmHU3qQMpTHXisG23AO_-Qy4y3gXBBtWt2_HhE.&isImagePreview=True]






******************************************************************************************************************
Experience the British Library online at www.bl.uk<http://www.bl.uk/>
The British Library’s latest Annual Report and Accounts : www.bl.uk/aboutus/annrep/index.html<http://www.bl.uk/aboutus/annrep/index.html>
Help the British Library conserve the world's knowledge. Adopt a Book. www.bl.uk/adoptabook<http://www.bl.uk/adoptabook>
The Library's St Pancras site is WiFi - enabled
*****************************************************************************************************************
The information contained in this e-mail is confidential and may be legally privileged. It is intended for the addressee(s) only. If you are not the intended recipient, please delete this e-mail and notify the [log in to unmask]<mailto:[log in to unmask]> : The contents of this e-mail must not be disclosed or copied without the sender's consent.
The statements and opinions expressed in this message are those of the author and do not necessarily reflect those of the British Library. The British Library does not take any responsibility for the views of the author.
*****************************************************************************************************************
Think before you print
https://listserv.loc.gov/cgi-bin/wa?A3=ind1704&L=PCCLIST&E=base64&P=2096855&B=--_000_CCBD2B86DCB53548A6F812DC1E09A2EC0104C6A29CV8BEXCHANGE01_&T=text%2Fplain;%20charset=utf-8&header=1
listserv.loc.gov
crawl=CC-MAIN-2022-05
13429
application/http; msgtype=response
sha1:B4KGFVCIZIN4ES2PYYNYDQ7ZOQPWDQ7B
<urn:uuid:f5356f48-8952-4277-aa29-fad91be05411>
2022-01-23T00:55:41Z
140.147.239.86
text/html
sha1:3G2PTEDGEGXLCBZL7JCKMD4KV7FE26C6
<urn:uuid:fab3d1e0-3cb5-4594-997c-5fe18f046d3f>
https://listserv.loc.gov/cgi-bin/wa?A3=ind1704&L=PCCLIST&E=base64&P=2096855&B=--_000_CCBD2B86DCB53548A6F812DC1E09A2EC0104C6A29CV8BEXCHANGE01_&T=text%2Fplain;%20charset=utf-8&header=1
response
<urn:uuid:d74492e8-8f10-4c65-b8fc-652e58a5e251>
isPartOf: CC-MAIN-2022-05
publisher: Common Crawl
description: Wide crawl of the web for January 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-95
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.3-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/