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 2015

BIBFRAME May 2015

Subject:

Re: Series in BIBFRAME

From:

Kathleen Lamantia <[log in to unmask]>

Reply-To:

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

Date:

Tue, 26 May 2015 19:23:45 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

Joseph,

Thank you for framing these questions/problems so well.

Kathleen F. Lamantia, MLIS
Technical Services Librarian
Stark County District Library
715 Market Avenue North
Canton, OH 44702
330-458-2723
[log in to unmask]
Inspiring Ideas ∙ Enriching Lives ∙ Creating Community
 
-----Original Message-----
From: Joseph Kiegel [mailto:[log in to unmask]] 
Sent: Tuesday, May 26, 2015 2:04 PM
To: [log in to unmask]
Subject: [BIBFRAME] Series in BIBFRAME

We are having difficulty understanding how BIBFRAME will describe series. 
It seems best to step back to look at requirements for an adequate description and linking of series, and then to see how well BIBFRAME currently meets these requirements.

First, a look at the WEMI model and what it tells us about series.

1)  Series is often manifestation-level information.  That is, the work Hamlet is not in a series, nor is an English language expression of Hamlet. 
Rather, one manifestation of Hamlet published by Clarendon Press is in the Oxford Shakespeare series, another manifestation published by Cambridge University Press is in the Cambridge pocket Shakespeare series, and many manifestations of the work are in no series.

2)  It follows that the relationship between a WEMI entity and a series as a related work is often between a manifestation and its related series work, not between a work and its related series work.  It is the Clarendon Press Hamlet (manifestation) that has the related work Oxford Shakespeare series. 
(There are also cases where a work has a related series work, e.g. a subseries and the series in which it is published.)

3)  Series numbering is related to a manifestation and is not part of the name of a series as a related work.  SPIE proceeding series ; v. 2357 as a statement on a manifestation means that this manifestation has a relationship to the work “Proceedings of SPIE—the International Society for Optical Engineering”.  “v. 2357” is not part of the name of the related series work:  it must be accounted for as manifestation information.

4)  The ISSN of a series is an identifier of the series, not an identifier of a manifestation in which the ISSN appears.  0277-786X is the ISSN of the SPIE proceedings series:  it does not identify volume 2357 of the series.

Next, a look at RDA.  Transcription of series information is core in RDA, which means that it is required when series are present.  Linking to related series works is optional, according to local cataloging policy.

Looking at examples, we find a number of data elements present in series statements.  Examples below are given in ISBD punctuation rather than MARC coding.

Title proper
Subtitle
Parallel titles
Statement of responsibility
Series numbering
Subseries title proper
Subseries numbering
ISSNs
Multiple series on a single manifestation Other data elements for complex situations (e.g. different volumes of a multivolume set in different series)

Example with title proper, numbering, ISSNs, parallel titles, and multiple
series:
International archives of photogrammetry and remote sensing, 0256-1840 ; v. 
30, pt. 3 = Internationales Archiv der Photogrammetrie und Fernerkundung ; Bd. 30, Teil 3 SPIE proceedings series, 0277-786X ; v. 2357

Example with title proper, statement of responsibility, numbering, subseries title proper, and subseries numbering:
Publication / Field Museum of Natural History ; 239-240. Zoological series ; v. 16

Example of different volumes in different series:
Bd. 5-6: Annales Universitatis Saraviensis. Serie Philosophie. Beiheft Bd. 7-8: Annales Universitatis Saraviensis. Reihe: Philosophische Fakultät Bd. 9: Veröffentlichungen des Instituts für Landeskunde des Saarlandes


A minimum set of requirements for BIBFRAME would seem to be:

*Support transcription of series information in Instances.
*Provide a structure in Instances that keeps associated information together, e.g. when multiple series are present, keep ISSNs and series numbering associated with the correct series title.
*It would seem to be good practice to provide separate properties for title proper, subtitle, parallel title, statement of responsibility, numbering, subseries title proper, subseries numbering, and ISSNs.
*Record ISSNs as series identifiers.
*Support linking from both Works and Instances to related series works.
*Handle series numbering as Instance information.


The current BIBFRAME properties for series, bf:series, bf:subseries and bf:issn, do not meet these requirements:

bf:series seems intended to provide a link to related series works, but its domain is bf:Work instead of being unspecified.

bf:subseries seems intended to do the same and has the same problem.

bf:issn is intended as an identifier of an Instance rather than a series.
 

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

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