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
[log in to unmask]
Inspiring Ideas ∙ Enriching Lives ∙ Creating Community
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.
Statement of responsibility
Subseries title proper
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
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.