LISTSERV mailing list manager LISTSERV 16.0

Help for BIBCO Archives


BIBCO Archives

BIBCO Archives


BIBCO@LISTSERV.LOC.GOV


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

BIBCO Home

BIBCO Home

BIBCO  December 2010

BIBCO December 2010

Subject:

Re: Forms of Names in Authorities (was: Status ... Part Two)

From:

Deborah Tomaras <[log in to unmask]>

Reply-To:

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

Date:

Mon, 6 Dec 2010 10:44:18 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (77 lines)

Thank you, Mr. Brenndorfer, for explaining why RDA has chosen to change the
name authority descriptors from titles of position etc. to free-text
descriptions, as shown in Mr. Schiff's document
http://faculty.washington.edu/aschiff/BCLAPresentationWithNotes-RevAug2010.pdf
. He wrote: "Many of the new elements in RDA for attributes of persons
(some of which can be used in authorized access  points) come from FRAD
(Functional Requirements for Authority Data). However, some additions to
AACR2 headings such as titles of position or office, initials of academic
degrees, and initials denoting membership in an an organization, do not
correspond to FRAD elements. The elements in FRAD are derived from a
comparison of authority elements used in other metadata standards and in
European cataloging. The wider issues here are the internationalization of
authority data and crosswalk enabling between different metadata
standards."

I realize that such descriptions of profession/activity are--as "Dr." and
its ilk are in AACR2--intended to be a last ditch effort at
differentiation, after all else has failed. But we do come to that point
not infrequently, so need to consider how it would impact searching, recall
and future differentiation of names. I have already pointed out, in my
previous email, ways in which I think these free-text terms will be
detrimental to all of the above purposes. A further example, that I haven't
yet mentioned, of why I find free-text descriptors problematic is the
biases often appearing in such terms. I've already mentioned Rev. Jane
Brown, and the problem of gender related to the term "Clergyman". Even more
than that, though, under the rule change Rabbi George Brown and Imam George
Brown would also have to be described as "Clergyman", if no other
differentiating information is available. This reveals a further,
Christian-centric bias to the term, which some users might find, frankly,
offensive. Do we really want to recreate in the name authority file the
biases that have plagued the subject authority file, which are periodically
addressed with sweeping global changes (i.e., "older persons" in place of
"aged" etc.)? Or leave our catalogs open to the user complaints that would
result, and accusations of bias?

Even leaving aside the problematic nature of the parenthetical descriptors,
I believe the RDA change from titles etc. to descriptors, while
well-meaning will not aid in either the internationalization of data, or
its interoperability. Since VIAF and other databases already link different
authorized forms of name, without the rule change, I don't even see why
this is necessary (search "Bergmann, Werner, Dr. phil." in VIAF, and you'll
see the differing French and Israeli forms of the name peacefully
coexisting with the NACO form). But leaving this aside, I would imagine
that a German or French library, for example, would prefer "Brown, George,
Dr."--a term of address which appears in both languages--to an
English-language descriptive term, that their audiences might not be
familiar with. And especially since terms of address would be traced in the
245 under RDA rules, wouldn't it make more sense if comprehensibility to
foreign audiences is the goal to use words like "Rev.", which could be
puzzled out with reference to the 245, instead of "Clergyman", which
appears nowhere else in the bibliographic record, and is in a language that
isn't necessarily the primary language of all international library users?
Finally, I wonder what other metadata schemata were used as the basis for
the rule change, since some, including MODS and CDWA, for example, suggest
using the LCNAF/NACO authority file as the basis for their name entries.

I understand that in an increasingly complex and digital world, catalogers
also want their information to play nice with others. But I also believe
that, at base, metadata schemata (of which cataloging rules are one) are
developed not primarily to be interoperable--though it is desirable--but to
suit the needs of the users of the schema. And I am not convinced that
either catalogers or end users are being well-served by the proposed
changes, especially with regards to authorities.

Deborah Tomaras, NACO Coordinator
Librarian II
Western European Languages Team
New York Public Library
Library Services Center
31-11 Thomson Ave.
Long Island City, N.Y. 11101
(917) 229-9561
[log in to unmask]

Disclaimer: Alas, my ideas are merely my own, and not indicative of New
York Public Library policy.

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

May 2019
April 2019
March 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
November 2017
September 2017
August 2017
July 2017
May 2017
April 2017
March 2017
January 2017
December 2016
September 2016
August 2016
July 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 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
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
September 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
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
September 2004
August 2004
July 2004
May 2004
March 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
April 2003
March 2003
January 2003
December 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
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
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
October 1999
September 1999
August 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

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager