LISTSERV mailing list manager LISTSERV 16.0

Help for PCCLIST Archives


PCCLIST Archives

PCCLIST Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

PCCLIST Home

PCCLIST Home

PCCLIST  May 2012

PCCLIST May 2012

Subject:

Re: Use of field 678 with corporate body history

From:

"Moore, Richard" <[log in to unmask]>

Reply-To:

Program for Cooperative Cataloging <[log in to unmask]>

Date:

Thu, 24 May 2012 16:11:22 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (128 lines)

Chuck

None of the new data in name authority records, including 678, is required, in the sense of being an RDA Core element. We're asking our NACO cataloguers to include the new metadata elements when the information has been turned up in the course of the research needed to create and jusify the access points, but not to do additional research for completeness. I can't see us often having the time to add a 678, unless there's a handy chunk of text that can be copied and pasted.

Regards
Richard
_________________________
Richard Moore 
Authority Control Team Manager 
The British Library
                                                                        
Tel.: +44 (0)1937 546806                                
E-mail: [log in to unmask]                            
 

   

-----Original Message-----
From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Herrold, Charles
Sent: 24 May 2012 15:31
To: [log in to unmask]
Subject: Re: [PCCLIST] Use of field 678 with corporate body history

       This question is not intended to be confrontational, but I have to ask: Is the 678 field going to be expected on Day One, or is it optional?  Two related things come to mind: first, the information therein is largely derived from 670 fields, and it seems like a possible waste of time to rephrase that data, though I understand the purpose would be for public display; second, some OPACs do not display authority records, and therefore public display of this field is not an option.
       I've seen RDA authority records (or AACR2 records with added RDA elements, of course) that look like miniature biographies.  All well and good, but I wonder how many minutes (or hours?) it were required to prepare some of these voluminous records.  A fundamental purpose of ARs, as I understand it, at least in the current pre-RDA era, is to precisely identify and disambiguate, and the new approach goes far beyond what is necessary to accomplish that goal.
       As a longtime music cataloger, I see the value of the new 38X fields that could be used to limit searches to performance medium, key, and so forth, and I expect NMP (NACO Music Project) will eventually initiate some sort of project to add that data to work records for musical compositions.  I also do appreciate the potential use of 37X fields.   
       Some have promoted RDA by emphasizing its many options for catalogers.  If in fact the exercise of options would allow varying degrees of fullness in authority records, that would be a good thing. (I have added birth dates and so forth to many thousands of ARs over the years, so I am not lazy.)  I'm just wondering how much extra data, beyond that serving the critical goal that I've postulated, will be required.     
Chuck Herrold
Carnegie Library of Pittsburgh


-----Original Message-----
From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Cristan, Ana Lupe
Sent: Thursday, May 24, 2012 9:06 AM
To: [log in to unmask]
Subject: Re: [PCCLIST] Use of field 678 with corporate body history

Hello Adam,
FYI - the February 2012 update of the Descriptive Cataloging Manual http://www.loc.gov/catdir/cpso/dcmz1.pdf contains information on use of the 678 field.

Ana Lupe Cristán
Library of Congress
Policy and Standards Division
101 Independence Ave.
Washington, DC 20540-4305
Tel. +1.202.707.7921
fax +1.202.707.6629
Email: [log in to unmask] 


-----Original Message-----
From: Program for Cooperative Cataloging [mailto:[log in to unmask]] On Behalf Of Adam L. Schiff
Sent: Wednesday, May 23, 2012 7:11 PM
To: [log in to unmask]
Subject: Re: [PCCLIST] Use of field 678 with corporate body history

The 678 field was not used in NACO records done under AACR2.  If you look at the old MARC 21 Authority: LC Guidelines ("Blue Pages") for this field it was marked as: "NACO: Do not use this field."  The LC Guidelines are now revised and say: "NACO: May be supplied in a NAR coded 008/10 c or z."

So, the 678 can now be used for AACR2 or RDA records, but this is only a very recent change, and you won't find the examples in the MARC documentation in name authorities.

Here's a family name in RDA that has a 678: no2012067728 Romanov (Dynasty
: 1613-1917)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Adam L. Schiff
Principal Cataloger
University of Washington Libraries
Box 352900
Seattle, WA 98195-2900
(206) 543-8409
(206) 685-8782 fax
[log in to unmask]
http://faculty.washington.edu/~aschiff
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

On Wed, 23 May 2012, Ian Fairclough wrote:

> PCCLIST readers,
> 
> Although the MARC 21 Format for Authority Data gives an example of 
> usage of field 678 Biographical or Historical Data, I am not aware of actual usage in name authority records.   The example is:
> 
> 678 1# $aThe Office of Geography provides research and other staff 
> services for the interdepartmental Board on Geographic Names and the 
> Secretary of the Interior on foreign geographic nomenclature.$bThe Office inherited functions and records of earlier boards and committees engaged in similar work. The earliest of these, the U.S.
> Board on Geographic Names, was created by an Executive order of 
> September 4, 1890, to ensure uniform usage throughout the executive departments of the Government ...
> 
> I searched "Office of Geography" in the NAF and retrieved 15 NARs, but 
> none of them had a 678 field.  The one that looked like it might have been the basis for the example, "United States. ?bOffice of Geography", had this note:
> 
> 667  The Division of Geography was created in the Dept. of the 
> Interior in 1947. In 1955 the division was renamed Office of 
> Geography. In Mar. 1968 the functions of the Office of Geography were transferred to the Geographic Names Division of the Army Map Service (after Jan. 16, 1969, Army Topographic Command).
> 
> So field 667, a Non-Public General Note, was used rather than field 
> 678, rather than field 678, which under Field Definition and Scope has: "Usually written in a form adequate for public display."
> 
> Did field 678 simply go out of fashion?  Has there been a technical 
> reason for its non-use?  And are there in fact any systems which could 
> take advantage of such a note to display to the public?  (Not that 
> they would, if there aren't any 678 notes in any NARs to display!)
> 
> Ian Fairclough - George Mason University - [log in to unmask]
> 
>
This email message and any files transmitted with it are intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law.  Any use, distribution, copying or disclosure by anyone other than the intended individual or entity is prohibited without prior approval.  If you have received this information in error, please notify the sender immediately.



**************************************************************************
Experience the British Library online at http://www.bl.uk/
 
The British Library’s new interactive Annual Report and Accounts 2010/11 : http://www.bl.uk/annualreport2010-11http://www.bl.uk/knowledge
 
Help the British Library conserve the world's knowledge. Adopt a Book. 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 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

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager