LISTSERV mailing list manager LISTSERV 16.0

Help for BIBFRAME Archives


BIBFRAME Archives

BIBFRAME 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

BIBFRAME Home

BIBFRAME Home

BIBFRAME  September 2011

BIBFRAME September 2011

Subject:

Re: Description and Access functions in a post-MARC environment?

From:

Hal Cain <[log in to unmask]>

Reply-To:

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

Date:

Thu, 15 Sep 2011 02:37:16 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (64 lines)

On Wed, 14 Sep 2011 11:21:25 -0700, Karen Coyle <[log in to unmask]> wrote:

>Peter, I was hoping we'd hear from some catalogers, but here's my take:
>
>The transcribed parts are intended to be a surrogate for the title
>page (primarily). That way, if you have metadata for two books (or one
>book and metadata for a similar book) you should be able to compare
>the transcribed fields and see if they are the same.

OK, I'll bite (hoping that a retired cataloguer counts)!

Transcription is intended to match what's on the title page (or other 
principal identifying matter).  As others go on to explore, it's an 
imperfect match. However it does matter a great deal, because we need also 
to match what writers do when they create a citation for what the give as 
sources, additional reading, reference lists, systematic bibliographies, and 
it needs to be able to respond to searches which depend on informal 
citations too -- comments in academic lectures or conference presentations, 
word of mouth information, passing citations in radio and television talk.
>
>HOWEVER...
>
>Not all of the transcribed data is transcribed "as is." For example,
>the case of titles is changed to sentence case, regardless of the case
>of the title on the title page. This is because the title, like so
>many data elements in cataloging, performs more than one function in
>the catalog record. It is both a surrogate (which in fact it isn't
>quite) and an entry element.

Sentence case, title case or all caps, and font, are a style choice of the 
publisher's graphic designer, and don't affect the information content of 
the title page -- if they do (as in  interlaced parallel titles with words 
common between languages) special account may have to be taken of them.

>The concept of providing a surrogate for the title page is a useful
>one, IMO, but the "sorta/kinda/almost" way that it is done in
>cataloging makes it less useful.

Not much less -- for textual works, anyway.

Ed Jones <[log in to unmask]> points to a notion that I too have considered:

>Would transcription still be necessary if a title page (or analogous source 
for other types of resource) image were routinely included along with the 
metadata as part of a catalog record "package"?

Not all conveyance of bibliographic information is web-based, nor is it 
carried out by experts. Therefore I think the transcription-based rendering 
of the most essential recognition elements (author/creator/etc., title, 
place, publisher, date, edition if not first, ISBN -- and equivalent for 
other than textual resources) remains necessary -- we can't count on having 
a linked t.p./cover image always associated with these essential recognition 
elements.  

Note, as an aside, that "place" (of publication) was omitted from RDA "bare" 
core elements; I disagree with this omission, on the grounds that I continue 
to read recently-released, substantial books which persist in giving place 
but not publiher's name in the bibliography.

Hal Cain (actively cataloguing till 2 months ago)
Melbourne, Australia [who says major jurisdiction isn't needed for 
recognition of place?]
[log in to unmask]

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

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager