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

BIBFRAME May 2013

Subject:

Re: Consistency

From:

"Tennant,Roy" <[log in to unmask]>

Reply-To:

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

Date:

Wed, 29 May 2013 14:49:34 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (71 lines)

On 5/28/13 5/28/13  10:48 PM, "Bernhard Eversberg" <[log in to unmask]>
wrote:

>Consistency is not hugely important for purely descriptive data...
>
>Consistency is of utmost importance for access-related data.

Agreed. But we nonetheless seem to have focused too much on consistency of
descriptive data (for example, "ill." in collation statements) and yet not
enough in access-related data (for example, we are unable to consistently
determine when a URL will take the user to the full item).

And as the table that my colleague Ralph LeVan provided earlier
demonstrates, our data is horribly inconsistent in the aggregate.

Here is but a beginning list of the problems we face in trying to be
consistent:

1) Rules that are inexact or difficult to understand.
2) An unclear understanding, or an imperfect use (whether deliberate or
inadvertent), of those rules.
3) Typographical errors.
4) Data acceptance systems (either single record or batch) that fail to
validate appropriate elements.
5) Violation of rules for local purposes (for example, putting data in a
different element so it will display in a particular system; or adding
HTML markup to elements for local display purposes).
6) etc.

I'd like to assert that these problems are in our past, but I clearly
cannot. Let's take the 264 field for example[1]. Recently created, these
fields are now pouring into WorldCat (in Jan. we found 56,706 such fields
and in April we found 158,019 -- nearly three times as many). Meanwhile,
the rules seem fairly specific about what one should do if the place of
publication is not apparent[2]: put "[Place of publication not identified]
:" in the $a. Not any of these:

[Place of publication not identified :
[place of publication not identified] :
Place of publication not identified :
[Place of publication unknown] :
[Place of publication not given] :
Unknown place of publication :
[place of publication not indicated] :
[Place of publication not known] :
Unknow place of publication :
No place of publication :
Place of publication unknown :

All of which (and more) already occur[3], and more still as they continue
to pour in.



So I guess my point is this: we all need to own this problem and work
against the forces of inconsistency outlined above and others that may
occur to you. These will include a wide variety of techniques that must
encompass the entire library metadata ecosystem -- from the individual
cataloger to the massive aggregators like my employer.
Roy Tennant
OCLC Resarch

P.S. And please don't get me started on that colon. One rant per day is
quite enough.

[1] http://experimental.worldcat.org/marcusage/264.html
[2] http://www.loc.gov/marc/bibliographic/bd264.html
[3] http://experimental.worldcat.org/marcusage/pob.txt and for additional
amusement, see all the ways "New York" has already been entered here:
http://experimental.worldcat.org/marcusage/ny.txt

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

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