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

BIBFRAME November 2011

Subject:

Re: Top-down or bottom-up? Example for a simple web service

From:

Bernhard Eversberg <[log in to unmask]>

Reply-To:

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

Date:

Tue, 22 Nov 2011 11:19:31 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (65 lines)

Am 21.11.2011 17:14, schrieb J. McRee Elrod:
>
>> Usefulness
>>    Cover all usage requirements
>>    Form supports function: Minimize effort of the user
>>    Flexibility: Openness for future requirements and new options
>
> Later you address interfaces, but do not explicitly mention *display*,
> a function well met by Avrom's orriginal MARC design (but ignored by recent
> additions); and met by AACR2, but ignored by RDA.
>
In Avram's time, display was the only task for the data, card
production was MARC's raison d'Ítre.
And for the cataloging rules, card layout was eminently important
because the card was at once the product of cataloging *and* the user
interface.

Now, the product of cataloging has to fit into many more environments
but no longer into card drawers. Accordingly, data have to meet many
new requirements. Beside human-readable displays, we have to create
services that deliver machine-actionable data. This is where our
legacy stuff is very deficient and inconsistent, and RDA hasn't quite
arrived in that world either.
RDA does not ignore ISBD altogether, but it assumes that catalogers
have no direct business any more with the user interface. The pasting
together of an ISBD display, in other words (or any other, for that
matter), ought to be a purely automatic process, and that includes the
insertion of punctuation.

And LC's 2008 report on the Future of Bibliographic Control
(http://www.educause.edu/Resources/OntheRecordReportofTheLibraryo/162443)
clearly stated:
   "4.1 Design for Today's and Tomorrow's User"
which may be understood to imply less or no regard for yesterday's
user's expectations.

And yet, for all the new qualities and functionality our data are
supposed to have, the end products will have to satisfy the needs of
humans - as long as machines don't replace the readers.
I.e., something will always have to be displayed for human consumption.
However, that includes a lot more than just displays of single catalog
records, like search results in various stages, index listings,
navigation through subject headings and classifications ... all
derived from catalog data but not guided by RDA (or AACR) either. And
then add to all that all sorts of enrichment stuff in the widest sense,
not covered by any cataloging rules at all.

The display issue itself is rather old:
The loss of a standardized user interface in new OPACs, and the loss
of influence of catalogers on that interface,  was the subject of a
series of postings to Autocat in about 1994, under the
title "Face the Interface". Nothing much ensued back then but
around 2003, IFLA ran a Task Force on Guidelines for OPAC displays, and
Martha Yee came up with a still recommendable report. Search for
"Martha Yee" "opac displays" to find out more, or 
"YeeOPACGuidelines.pdf" (containing a list of 37 principles). Even at
that time, machine actionability was not a subject, nor web services.
But by no means do those new subjects make the old issues of human
interpretability of displays go away. And yes, it should still serve
libraries well to have a recognizable standard for bibliographic data
display, applied and understood the world over.


B.Eversberg

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

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