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

BIBFRAME September 2011

Subject:

Content Data vs. Textual Data

From:

Jeffrey Trimble <[log in to unmask]>

Reply-To:

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

Date:

Tue, 27 Sep 2011 10:07:33 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (53 lines)

I've been thinking about this issue because it is an interesting way for Catalogers, Data Analysts and Librarians to look at the issue.  This also plays into
the Cataloging thinking of "transcribing a title" and the interesting new feature(s) of RDA.  Let me remind you that I'm doing this on the cuff, so some things
are not presented "pretty" or necessarily logical--I'm thinking aloud.

So we have this MARC record structure.  As I have been mentioning before, it is possible to expand the structure.  For the sake of this discussion, let's assume
we were to expand the Indicators from 2 to 3.  The new indicators has definitions of:

0	This is textual data [transcribed]
1	This is content data [transcribed]
2	This is textual data [non-transcribed]
3	This is content data [non-transcribed]
4	This is transcribed data (textual and content)
5	This is non-transcribed data (as it appears on a title page or on the item textual and content)

...  maybe more.

1.	Transcription Solution:

So you could then define a 245 in two  ways:

245 104  The adventures of Huckelberry Finn / $c Samuel Clemens.
245 005   The ADVENTURES of HUCKELBERRY FINN /$c samuel CLEMENS  <== Appears on the t.p.

Noticed that I actually used indicator position 1 to indicate indexing (printing or not printing on the card). Now the ILS vendor has to make it possible when two 245s are present to make sure these indicators work correctly or you will either have duplicate entries.  (And filing can be a problem if the ILS does not normalize the character string when indexing and gives different weighting to upper case letters and lower case letters.

2.  Content vs. textual.

300 ##0 $a xii, 543 p. : $b ill., maps ; $c 28 cm.
300 ##1 $a xii $a 543 $ap. $bill $b maps $c 28 cm. 

You can now teach the display to see the second 300 hundred as content data and the computer knows roman numerals from non roman.

3.  Example with Imprint statement

260 ##0	[New York, N.Y.] : $b Moonshine Press, $c c1990.
260 ##2   NEW YORK :$b MoonSHINE,     <==appears on t.p., but no date until you turn to t.p. verso.
260 ##1   New York, New York : $b The Moonshine Press, $c 1990, $g 2008

Do you see where I'm going with this.  We are able to record data in a variety of ways and let the machine manipulate it as needed.  The subfield codes can more or less stay the same, but we still may need to expand on this area.

--Jeff


Jeffrey Trimble
System LIbrarian
William F.  Maag Library
Youngstown State University
330.941.2483 (Office)
[log in to unmask]
http://www.maag.ysu.edu
http://digital.maag.ysu.edu
""For he is the Kwisatz Haderach..."

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