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

BIBFRAME June 2014

Subject:

Re: Thoughts about Bibframe

From:

"[log in to unmask]" <[log in to unmask]>

Reply-To:

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

Date:

Thu, 26 Jun 2014 10:26:56 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (33 lines)

Phil--

That is a great example. I didn't for a moment intend to imply that moving from models of description based around records to models based around fine-grained assertions isn't going to have really good outcomes for patrons: I sincerely believe that it will and that it's a very important task. My concern was more to the area of process. I was wondering how use cases like the one you outline below have been assembled and examined and used as a basis for the Bibframe work. For example, at "http://www.loc.gov/bibframe" neither the "Analyses" nor the "Use Cases" bullet is actually linked to anything. 

---
A. Soroka
The University of Virginia Library

On Jun 25, 2014, at 12:12 PM, Philip Evan Schreur <[log in to unmask]> wrote:

> I totally agree here!  I'm headed to ALA right now and hope to write more later but let me give one example of where Bibframe makes huge strides for users.  Music has been very I'll served by MARC, the combination of complex data, multiple works contained in a single resource, and a flat file structure makes discovery extremely difficult.
> 
> Bibframe allows you to include information such as performers, subject headings, timings, etc. in the individual bf:work areas for each individual resource in a multiple-resource collection( I.e. Sound recording).  All those false drops in searching that are pervasive in discovery systems now that are based on MARC can be eliminated.  This is a HUGE win for us music folks.  A brilliant solution and directly user focused.
> 
> Philip Schreur
> Stanford University
> 
> Sent from my iPhone
> 
>> On Jun 25, 2014, at 8:45 AM, "[log in to unmask]" <[log in to unmask]> wrote:
>> 
>> Amen.
>> 
>> I'll add my own thought: the notions of "use case" and "functional requirement" are most powerful and meaningful when they are centered on _patron_ uses and requirements for functions exercised by _patrons_ (as opposed to _librarians_, using the term broadly: I mean to distinguish between those who are served and those who serve). It is not very clear to me by what process ideas about patron uses and requirements have informed the construction of Bibframe.
>> 
>> ---
>> A. Soroka
>> The University of Virginia Library
>> 
>>> On Jun 25, 2014, at 10:34 AM, Karen Coyle <[log in to unmask]> wrote:
>>> 
>>> Nowhere, however, do a see a serious discussion in the library data creation community of use cases and functional requirements. (And, believe me, FRBR does not provide this.) Many of the elements that have been added to MARC over the years (after taking many hours of discussion within the MARC committee) rarely appear in actual library data. Yet more continue to be added. Where are we headed? Why? What is the result we seek?

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