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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

BIBFRAME Home

BIBFRAME Home

BIBFRAME  October 2014

BIBFRAME October 2014

Subject:

Re: Conceptuality of Work in Multi-volume Resources

From:

Leif Andresen <[log in to unmask]>

Reply-To:

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

Date:

Tue, 14 Oct 2014 12:46:33 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (97 lines)

The problem here is, that not all possibilities of BIBFRAME is used.

With the users perspective, the metadata about Work and Instances shall be used for presentation in an user interface.

To make it simple: The user search for Hamlet and the data base have to works:

WORK 1: Hamlet
WORK 2: Shakespeare's complete writing

With the 1:1 principle from the Bibliographic Framework as a Web of Data: Linked Data Model and Supporting Services (November 21, 2012) you can only present for the user:

WORK 1: Hamlet - with a link to first page of the instance
WORK 2: Shakespeare's complete writing - with a link to first page of the instance (where Hamlet is on page 512)

But the reality is a bit more complex:
WORK 1 have an instance, and WORK 2 have one instance - but inside this instance you can find another instance Hamlet. And this Instance inside an Instance have a Instance-to-Work relation to WORK 1.

If we forget the 1:1 principle, the answer can be:

WORK: Hamlet
  With link to page 1 Instance of WORK 1
  With link to page 512 in Instance of WORK 2 - which also is Instance of WORK 2 with page interval 512-589

Of course you can present relevant pages according to search terms, but you can't express that pages 512-589 of the instance of WORK 2 also is an Instance of WORK1.

So: If we see a multivolume instance as an container for instances, we can use the relations to show that WORK 1 have instances both as individual instances and as parts of a multivolume - and the multivolume on the same time as a whole is instance of another work.

And of course the two works have a relation: one work as part of the other work.

We have a problem with the November 2012 document - but not with the BIBFRAME Vocabulary - all the needed relations is part of the Vocabulary.



Best regards,

Leif Andresen



Det Kongelige Bibliotek
Nationalbibliotek og Københavns Universitetsbibliotek
Leif Andresen
Chefkonsulent | Adviser to the Director

Det Kongelige Bibliotek | The Royal Library
Nationalbiblioteket - Stab | The National Library of Denmark - Staff
P.O. Box 2149 | DK-1016 København K
tel +45 9132 4366 | Fax +45 3393 2218 | [log in to unmask] | www.kb.dk

Besøgsadresse | Visiting address | Søren Kierkegaards Plads 1
Leveringsadresse | Delivery address | Christians Brygge 8 | 1219 København K

EAN 5798 000 79 52 97 | Bank 0216 4069032583 | CVR 28 98 88 42
IBAN DK2002164069032583 | Swiftcode DABADKKK








-----Oprindelig meddelelse-----
Fra: Bibliographic Framework Transition Initiative Forum [mailto:[log in to unmask]] På vegne af Nicolas Prongué
Sendt: 14. oktober 2014 13:54
Til: [log in to unmask]
Emne: Re: [BIBFRAME] Conceptuality of Work in Multi-volume Resources

Senan wrote:

"If a library is collecting an entire complete manga series and cataloguing it as such rather than individual volumes, then I think having the series act as a Work with each volume being an Instance is the logical conclusion."

As I understand it, I would say that the whole series (published by Publisher XYZ in English for example) is a BIBFRAME Instance. The various volumes would be registred as Holdings. And the series, regardless of any languages or publishers, would be the Work.

Best regards

Nicolas Prongué
Haute école de gestion de Genève

-----Message d'origine-----
From: Senan Kiryakos
Sent: Tuesday, October 14, 2014 3:33 AM
To: [log in to unmask]
Subject: Re: [BIBFRAME] Conceptuality of Work in Multi-volume Resources

Thanks for the replies (and to the split-off discussion with Reinhold and
Simon)

Minjie, FRBR Document 3.3 is just what I'm talking about, at least in regards to FRBR. Looking for a similar solution in BIBFRAME is where I am at the moment.

With regards to the conceptuality level of a 'Work', I understand that BIBFRAME's has less of a 'sky is the limit' view than FRBR, which is a good thing in my opinion. Going back to my One Piece example, in FRBR the Work level for One Piece could act as an umbrella entity for the manga, TV series, etc., but in BIBFRAME this overall conceptual level is not necessarily present, with connections between resources being made with relationships instead.

I think the core issue in the manga case is how resource specific should the BIBFRAME Work level represent. Perhaps the 'right' answer may depend on an institutions resources and their cataloguing practices. If a library is collecting an entire complete manga series and cataloguing it as such rather than individual volumes, then I think having the series act as a Work with each volume being an Instance is the logical conclusion. BIBFRAME certainly would allow each volume to be represented as a Work, with relationships being made between each one, but I don't know if this is a better solution (both conceptually and practically with regards to cataloguing practices.)

Thanks,
Senan Kiryakos

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