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  April 2011

PCCLIST April 2011

Subject:

Comments on RDA discussion paper

From:

"Adam L. Schiff" <[log in to unmask]>

Reply-To:

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

Date:

Wed, 13 Apr 2011 14:59:28 -0700

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (99 lines)

Comment that I have on the discussion paper:

Page 2: "It is likely that the JSC will continue to focus its attention on 
the development of RDA and that ALA will no longer revise AACR2."  ALA 
never revised AACR2 and does not have responsibility for it, although it 
is one of the publishers.  The JSC has responsibility for the content of 
both AACR2 and RDA, and it is safe to assume that the JSC has no interest 
in revising AACR2.  It is also highly unlikely that ALA could or would 
want to take this over, since it has a vested interest in promoting and 
selling RDA.  I think the quoted sentence would be correct if "ALA" were 
replaced by "JSC".

Page 2: "All existing BIBCO, CONSER and NACO documentation will need to be 
reviewed."  Depending on how the subject chapters of RDA are developed, 
perhaps SACO documentation will also need reviewing, but this is not as 
imminently needed.  However, given the changes to the forms of headings in 
RDA, it is likely that the Subject Headings Manual will need to be 
reviewed for obsolete forms (e.g., Bible headings; spelled out Department 
vs. Dept.).

Page 2: "PCC/AACR2 training is already in place and would not be developed 
further."  I agree, to an extent.  We have some excellent workshops on 
LCSH, LCC, name and series authorities, continuing resources and 
electronic resources, but we do not have a general descriptive cataloging 
course that would have been good to provide to both PCC and non-PCC 
libraries.  At regional and state library conferences that I go to, this 
always comes up as an issue, particularly for public libraries which often 
have just one cataloger who has to learn on the job without any help or 
mentoring.  I would love to see PCC take a lead in furthering the training 
of catalogers from all types of libraries so that the quality of records 
being created by these libraries is improved.

Page 2: "The Provider-Neutral/Aggregator-Neutral cataloging model of using 
one bibliographic record for all instances of an online resource will stay 
in place as a PCC sanctioned allowable exception for both serials and 
monographs."  There have been some cogent arguments on the RDA Discussion 
List about how this approach may prove to be unwise in an RDA context, 
particularly if and when we get to an RDA implementation scenario 1 
(relational/object-oriented database structure) - see 
http://www.rda-jsc.org/docs/5editor2rev.pdf

Page 3: "Existing AACR2 headings should be grandfathered in. Over time, 
guidelines may be developed for when an AACR2 heading should be upgraded 
to the RDA form."  This statement is too broad.  I think *most* existing 
headings could be grandfathered in, but there are some that will need to 
be changed to RDA for the sake of consistency.  Authorized Bible access 
points are one example.  All Koran headings will need to be changed. 
Access points for some other types of works too to avoid split files with 
some works of an author under one heading and others under a different 
one.  Selections of an author problably need to be changed to "Works. 
Selections" so that they all file together.  I don't think it would be 
desirable to have some access points for a jurisdiction under Dept. while 
newer ones established under RDA are under Department.  I think this 
sentence should be revised to say that a strategy for grandfathering as 
many AACR2 headings as possible should be developed, but that there are 
some kinds of headings that will need to be changed to RDA, and that 
LC/PCC should convene a group to make those determinations and provide 
guidelines.

Page 3: "Bibliographic records created under either rule set would use the 
form established in the authority file."  I think that this is a sensible 
approach, but then I also think that what you end up with is not truly an 
AACR2 or an RDA record and that these records should be marked in some way 
as being a hybrid between the two.  Perhaps in the 040 field we should 
repeat the subfield $e and provide codes for both AACR and RDA?:

040  $a XXX $b eng $c XXX $e aacr $e rda

That would certainly be a good indicator that the record is a hybrid of 
rules, although it would not specifically indicate which elements are 
AACR2 and which are RDA.

Page 3: "the PCC should formally adopt RDA" - I think this just is not 
worded well.  It implies that PCC should unadopt AACR2 and move to RDA 
exclusively.  Since there are PCC libraries that are doing all their 
cataloging in RDA, and I think we should keep them in the PCC, I think 
what should be said is that the PCC permits contributions following RDA 
and that it is committed to creating documentation and training for those 
libraries choosing to implement RDA.  I also think that if the national 
libraries implement RDA, the PCC policy should be to eventually move all 
members to RDA, so that it will no longer maintain AACR2 documentation and 
training.  Once a decision to implement nationally is made, then I think 
the PCC should set a timetable for moving all of its members to the new 
standard.

Adam Schiff

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
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