If you made a request for a title, the system would probably get the Work set of triples and all it's Instances, and if you didn't specify a format or anything, it would filter through to get the library's preference for lending out books (ie., maybe the ebook) or the first one available in circulation. That's what happens today; your system knows bib records but they are linked to multiple copies; it may not allow you to see the copy data, but it's all there.
You wouldn't have to do any heavy lifting yourself unless the system wasn't very smart.
The collocation of ISBNs for paper and hardback is handled not by keeping them both in the same "record" but by having a link between the two instances; it's the same effect for the end users.
Maybe a different use case will help. Suppose I want to make an ILL request for a book published by the same publisher (say, a Norton Critical Edition) in hardback and paperback. I don't care which I get--I just want "the book." If these are different Instances (because they have different ISBNs and we've decided with BIBFRAME not to "muddy" things), will I be able to request a copy of the book regardless of binding, or will I have to choose which binding (which Instance) to request? Any choice will reduce the number of candidates for filling my request, given that I'd be happy with either binding; but I don't want to make two requests and maybe tie up two copies.
One reason libraries have chosen to ignore differences in ISBN and describe both bindings of the same text block on a single bib record is to simplify this kind of request for users. How will BIBFRAME provide that option if different bindings are assigned to different instances?
I can imagine that for a book publisher or vendor, separating each ISBN as a distinct instance could be useful and necessary. Assuming BIBFRAME is intended for more than just libraries, will BIBFRAME have profiled applications such that a vendor's BIBFRAME profile would specify one ISBN per instance while a library's BIBFRAME profile would not? Or do we need one rule for all?
On Mon, May 20, 2013 at 12:44 PM, Ford, Kevin <[log in to unmask]> wrote:
Thanks for your email. I'd like to start my reply with your concluding question:
> Does Bibframe have to legislate boundaries between instances?
-- It's not so much that BIBFRAME is legislating, or must legislate, boundaries as there has been a misinterpretation of us experimenting with the splitting of MARC records into BIBFRAME resources as being prescriptive and absolute.
For the record, we've not made any absolute determinations. On the contrary, we're experimenting. We're experimenting because we cannot see all the answers or possibilities. We are, on the other hand, open to them. That does not obviate multiple ISBNs per Instance in the future, but that's not our starting point. Nor do we harbor a fantasy that such an idea (that each ISBN *suggests* a different Instance/Manifestation) does not have its problems and does not have its own implementation costs, especially when we want to create a division in a MARC record where said division can be so nebulous. We do think ISBNs represent a pretty decent starting point for identifying different Instances (but ISBNs are not the only factor in identifying different Instances).
We would like to bring a little more order to bibliographic description, and that involves an attempt to bring greater clarity and demarcation to bibliographic description itself. As you noted, it is basically the exact same issue the cataloger faces when deciding to create a new MARC record. When to create a new BIBFRAME Instance? We're using the exercise of splitting MARC records into BIBFRAME resources as an aid in answering the question, or at least informing our answer.
> There are also cases where one copy of a book doesn't have
> an ISBN and a newer printing does, but they aren't
> otherwise different.
-- The Work/content is the same, but the two copies you describe would likely have differences that would suggest two different Instances (or
Manifestations). Would they not have a different publication date?
> Another problem with ISBN-based Instances is that since
> libraries have not historically tracked most hardback and
> paperback editions separately, they won't know which Instance
> to attach their holdings to. I suppose this could be resolved
> by libraries' asserting that certain ISBN-based Bibframe
> Instances are the same for their purposes and linking to that
> group of Instances.
-- This is what we commonly encounter. For me, it also describes how MARC records can muddy things a little. To which ISBN does the information in the 260 and 300 fields refer? The answer - by practice - is the first ISBN. In any event, there could be - and often are - significant publication and physical differences between hardback and paperback books that suggest to me they would better be treated as two distinct Instances of the the same Work. Sometimes the holdings record contains a clue about whether the copy is paperback or hardback. Relationships between Instances may be needed (though one could also leverage their shared relationship with a distinct Work).
As for the resources you mentioned without ISBNs, yes, the cataloger will need to make a decision and I suspect they will have guidance on along the same lines as the two references you cited.
On 05/19/2013 11:26 PM, Kelley McGrath wrote:
> On another thread, Kevin Ford said
> "... the challenge is clearly identifying Instances of Works. Different publishers/places of publication/dates is one of those 'split' points. ISBNs are equally attractive."
> Clearly identifying separate Instances is a hard challenge. It is not, however, a new challenge. It is essentially similar to the problem we currently face when trying to decide when to make a new MARC bibliographic record. Unlike Bibframe, MARC is silent on this point, but OCLC has pages and page on this at http://www.oclc.org/bibformats/en/input.html and ALA has a whole book (http://www.ala.org/alcts/resources/org/cat/differences).
> Libraries have traditionally been stronger lumpers than Bibframe's proposal to split Instances on ISBNs and have put what has been considered to be essentially the same printing on the same record. Lumping does a few things:
> *It reduces the proliferation of duplicates in databases
> *It reduces the number of records that have to be created (in the current system it is easier to reuse an existing record)
> *In existing catalogs, near duplicates are usually not helpful to patrons when they are navigating results lists and often make the process of placing holds inefficient (FRBRization helps with this somewhat and future systems may make this less of a problem)
> There is also the practical problem of how to know whether the book you're holding in your hand is a match for a particular record (or Instance). When something doesn't seem to fit, it might be that you have a different thing or it might be that the creator of the existing metadata has omitted some information, added some erroneous information (this often happens when a cataloger has "derived" a new record from an existing one, but there are other causes) or has interpreted the information on the item differently.
> Sometimes even comparing two books side by side, it can be difficult to tell. I am currently involved in a cleanup project in preparation for an ILS migration. One of our problems is that we have old retrocon records that were matched to OCLC records in an automated reclamation process with the result that we ended up with many cases of two records bearing the same OCLC number. Either the two things are the same and should be on one record or they are different and one of them needs to be matched to a different OCLC record number.
> My examples from this project are pre-ISBN era books, but I imagine the problem has not vanished (I am not primarily a book cataloger so don't have the experience to say). We had one case where two books had the exact same outward appearance and bibliographic information (title, publication info, pagination) except that one had "illustrated by X" on the title page. Upon examination, this book had unnumbered pages with illustrations whereas the other one had unnumbered pages with photographs. We put these on two records and I think you would consider them two Instances, but the only difference between the records is that one statement of responsibility. If a cataloger had only the illustrated book and the existing record didn't mention illustrations, it would be hard to know whether the record was describing something different or merely omitted some important data.
> On the other hand, we had a case where two books looked visually different, but again had the exact same bibliographic information except that one had "Phoenix Books" on the title page above the publisher's name. There appeared to be no difference in content. We put these on the same record. It seems unlikely that the presence of those two words would influence patrons' preferences. There are also cases where one copy of a book doesn't have an ISBN and a newer printing does, but they aren't otherwise different.
> Another problem with ISBN-based Instances is that since libraries have not historically tracked most hardback and paperback editions separately, they won't know which Instance to attach their holdings to. I suppose this could be resolved by libraries' asserting that certain ISBN-based Bibframe Instances are the same for their purposes and linking to that group of Instances.
> On the other hand, special collections and rare books cataloger often want to do more splitting than Bibframe. They want not just the ISBN, but the specific printing to be a separate Instance.
> Does Bibframe have to legislate boundaries between instances?
Stephen Hearn, Metadata Strategist
Technical Services, University Libraries
University of Minnesota
160 Wilson Library
309 19th Avenue South
Minneapolis, MN 55455