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: What's an instance?

From:

"Myers, John F." <[log in to unmask]>

Reply-To:

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

Date:

Sun, 19 May 2013 21:59:14 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (33 lines)

No. It is not an issue of patrons and display.  I believe Karen's "users" in this context are librarians and library systems.  She is saying that BibFrame development is going to go off the tracks if it continues in a fashion that is willfully ignorant of the realities of the "bibliographic data marketplace" -- the assumption of a one-to-one relationship involving the ISBN and the "Instance" is not tenable.  As articulated by others, despite the specification that ISBNs should be uniquely assigned, they aren't; conversely, different ISBNs are assigned to manifestations that librarians assess as equivalent (e.g. different bindings, same content). Then there are resources (contemporary and historical) to which an ISBN was never assigned and cases where individual and "collective" ISBNS also apply to a single item.  All of these failures of one-to-oneness, while perhaps a small number in the overall set of records, are nonetheless sufficiently significant (in both their number and the specific resources they impact) that a system predicated on a one-to-one arrangement will a) fail in the technical sense and b) be rejected, thereby failing in the commercial sense.

There's a joke that goes around in Navy circles: An aircraft carrier radios a distant radar contact that they are on a collision course and directs the radar contact to change course (since the carrier is bigger, more powerful, etc.).  The radar contact radios back that it is a lighthouse and the carrier can choose accordingly.

BibFrame is being told it's the aircraft carrier in this case.


John F. Myers, Catalog Librarian
Schaffer Library, Union College
807 Union St.
Schenectady NY 12308

518-388-6623
[log in to unmask]

________________________________________
From: Bibliographic Framework Transition Initiative Forum [[log in to unmask]] on behalf of Ford, Kevin [[log in to unmask]]
Sent: Friday, May 17, 2013 3:24 PM
To: [log in to unmask]
Subject: Re: [BIBFRAME] What's an instance?

> What your potential users (who may choose to become non-users pretty
> quickly) are telling you is that they have chosen this method because
> they do NOT want to present two different options to users where those
> options are not meaningful to the user.
-- By "user," I take it you to mean "patron" (this is fine, just want to be clear who the user is).  In that case, this is a display issue, and not directly within the the scope of BIBFRAME.  Do I think displays should find a graceful way to deal with such a skimpy Instance?  Absolutely.  Is it within the scope of BIBFRAME to solve that problem the issue of UI design? No.

More importantly, it should be borne in mind that this is first and foremost about data representation and exchange.  The BIBFRAME model need not determine how underlying systems store, crunch, or manage the data.

Kevin


> 

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