LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME Archives


BIBFRAME@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

BIBFRAME Home

BIBFRAME Home

BIBFRAME  April 2015

BIBFRAME April 2015

Subject:

Re: Work titles question

From:

Karen Coyle <[log in to unmask]>

Reply-To:

Bibliographic Framework Transition Initiative Forum <[log in to unmask]>

Date:

Tue, 21 Apr 2015 21:15:56 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (105 lines)

Adam, I think what you have demonstrated here is the difference between 
the act of cataloging and the resulting catalog data. The catalog data 
encodes the selected main creator and any secondary creators or 
contributors, but there is nothing in that data to provide evidence as 
to why the decision was made - e.g. if it was the order of the authors 
or the prominence of one author's name on the title page. If I show you 
a catalog record for a book you have never seen, you probably could not 
tell me what cataloging rule was used or what decision was made. Which 
is fine unless that information is essential for understanding the 
resulting catalog record.

Any information that is essential for the functionality of the catalog 
must be made explicit in the coding of the data. Any information that is 
not coded is not available to the developers of systems nor to the user 
of the catalog. In that sense, for the current discussion, the 
cataloging rules are only relevant to the extent that they can be 
understood from the resulting record. I am NOT saying that the decisions 
made by catalogers are not important -- what you describe below is 
essential for the consistency of data across libraries -- but no actions 
can be taken on machine-readable data except where the information is 
explicitly coded in the record itself.

So the question then becomes, of the information you give below, what is 
essential for the functionality of the catalog data once it is created? 
Or, to put it more bluntly, what do you want systems to do with the 
information you have given here? Then, once that has been clarified, the 
next question is: how can it be coded in the machine-readable data so 
that its meaning is clear?

kc

On 4/21/15 12:00 PM, Adam L. Schiff wrote:
> On Tue, 21 Apr 2015, Karen Coyle wrote:
>
>> There is no reason why we cannot have an ordered list of equally 
>> responsible creators where that is the case. But there is a 
>> difference between "first named author" and "main entry" -- and 
>> although catalogers may be aware that the main entry is often the 
>> first named author, the user looking at a library catalog display 
>> can't be expected to know what it means that one and only one author 
>> *heading* is listed with the short display. And, no, I don't think 
>> that the "statement of responsibility" explains all, even if it's in 
>> the display.
>
> While the "main entry" usually begins with the first named creator, 
> that is not always the case.  RDA 6.27.1.3 says that for collaborative 
> works, the work is named
>
> by combining (in this order): a) the authorized access point 
> representing the person, family, or corporate body with principal 
> responsibility
> b) the preferred title for the work
>
> If two or more persons, families, or corporate bodies are represented 
> as having principal responsibility for the work, construct the 
> authorized access point representing the work by combining (in this 
> order):
> a) the authorized access point representing the first-named of those 
> persons, families, or corporate bodies
> b) the preferred title for the work
>
> However, RDA notes that the entity with principal responsibility may 
> not necessarily be the first named entity.
>
> 6.27.1.3 goes on further to say:
>
> If principal responsibility for the work is not indicated, construct 
> the authorized access point representing the work by combining (in 
> this order):
> a) the authorized access point representing the first-named person, 
> family, or corporate body
> b) the preferred title for the work
>
>
> There are works in which the principal responsibility is indicated by 
> means of typography rather than by the order of the names in a 
> statement of responsibility.  RDA 6.27.1.3 has one such example:
>
> Bishop, Henry R. (Henry Rowley), 1786–1855. Faustus
> Resource described: Faustus : a musical romance / composed by T. 
> Cooke, Charles E. Horn, and Henry R. Bishop. Bishop's name is given 
> typographic prominence, appearing in all uppercase letters and in a 
> larger and different typeface from that of the others
>
>
> Adam
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> 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
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

-- 
Karen Coyle
[log in to unmask] http://kcoyle.net
m: +1-510-435-8234
skype: kcoylenet/+1-510-984-3600

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

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
July 2011
June 2011

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager