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: Holds and ILL with Bibframe

From:

Jörg Prante <[log in to unmask]>

Reply-To:

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

Date:

Thu, 23 May 2013 21:12:19 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (86 lines)

I'd like to give my version of explanation of the relation between FRBR 
and Bibframe.

The FAQ http://www.loc.gov/bibframe/faqs/ states quite briefly

"BIBFRAME Work identifies the conceptual essence of something; a 
BIBFRAME Instance reflects the material embodiment of a Work; a BIBFRAME 
Authority identifies a thing or concept associated with a BIBFRAME Work 
or Instance; and a BIBFRAME Annotation provides a new way to expand the 
description of a BIBFRAME Work, Instance, or Authority. "

Although close to the conceptual model of FRBR, Bibframe classes can be 
modeled by a sort of a "reduction" or "information extraction" procedure 
like this:

- extract all conceptual core descriptions from the FRBR classes - that 
is, what is author-controlled and not owned or handled by publishers, 
vendors, sellers, companies, intermediates, readers, libraries, patrons. 
It's the author's name, the title of the author's work, the mode of the 
work (text, sound, image, ...) Repeat that for an artist or a translator 
who realizes other work versions of the original work. Put that into 
bf:Work classes.

- extract all publisher-controlled information out of the FRBR classes - 
the name of the publisher, the decision about the publication structure 
(issuance, edition, version), the date and place of publication, the 
carrier, the physical extent, the tags like ISBN/ISSN, the prices for 
the product, all the addresses and names the publisher gave to the 
author's work etc. Put that into bf:Instance classes.

- extract all library-controlled information out of the FRBR classes - 
the formal description, the classification, the subject cataloging, the 
call number, the shelf location, authority control information, (maybe 
also descriptions of the library service for access to printed and 
electronic resources, it's not clear right now) etc. Put that also into 
bf:Instance.

- optionally, capture additional information that is created by 
companies/vendors/sellers/intermediates/readers and is somehow related 
to the author's work into bf:Annotation classes.

- optionally, lift some of the information recorded in bf:Work or 
bf:Instance to a "higher level of trust" by adding bf:Authority classes.

What helps me to understand the Bibframe model is the changing scope of 
information control over time, during the lifecycle of a work. It does 
matter who is allowed to add or modify information. This is reflected 
well in the Bibframe model.

I hope this makes sense, and demonstrates that Bibframe modeling by 
using a reduction procedure can also be applied to all kind of 
information found in bibliographic resources, be it MARC or another 
format, of course also RDA information sets.

Although, I would like a clearer separation of publisher-controlled and 
library-controlled information. It may help later to attach ONIX or 
something similar to Bibframe seamlessly, or an ontology for enterprise 
resource management. And most of the library's added information is 
metadata which is not changing the physical nature of the publisher's 
manifestation in bf:Instance. So bf:Instance sounds not like a good 
class name choice for that, maybe a new bf:Service class (as a subclass 
of bf:Instance) would be an option?

It reveals also there is a "metadata production chain" from the author 
to the reader/user, completely independent of library catalog rules. It 
can be predetermined which Bibframe data sets must be touched for the 
purpose of efficiently creating or updating catalogs. The less data sets 
must be touched for updates, the better (e.g. adding holdings to a union 
catalog).

And Bibframe can explain to the public what is happening with works in 
the library space. It helps tracking the path of a work from the 
author's idea of creating a work to the reader in the library who is 
searching for it. Still, Bibframe isn't complete yet, and needs a lot of 
contributions.

Jörg

Am 23.05.13 17:19, schrieb Laura Krier:
> I apologize if this is an issue that has already been covered, but I 
> just want to get some clarity.
>
> In BIBFRAME, a work might be approximately the equivalent of a FRBR 
> expression? An instance might be approximately equivalent to a FRBR 
> manifestation? And items would be expressed in annotations?

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

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