Stuart, this is a great example of ambiguous things with the same title. 
What I think we are missing is better use of bibliographic types (which 
I think should be subtypes of WEMI or bf:WI, but that's another 
discussion) to help disambiguate. There's a big difference between the 
treaty, the reference book about the treaty, and the reviews of the 
reference book about the treaty, which could be facilitated by taking 
the bibliographic type into account. I'm not sure that really helps the 
cataloger, but it could be a great boon to the user.

Right now, we show users physical formats and publishing patterns: book, 
journal, journal article, CD, DVD, ebook, etc. But we don't let them 
choose between a treaty, a reference book, and a book review. That 
information may be discernible from the bibliographic data, but it isn't 
presented in a usable way. At best it's hidden in a sub-section of a 
subject heading which a user only sees in a long display.

Identifiers (ISBN, DOI) will distinguish between these documents for 
machine processing, but other qualities are needed for the human 
information seeker.


On 2/24/16 4:00 PM, Stuart Yeates wrote:
> Maybe an concrete example might help explain one of the obvious issues 
> with authority control of works:
> We have a constitutional document here called the "Treaty of 
> Waitangi". The original  "Treaty of Waitangi" has been around forever, 
> so there's no problem finding URLs for authority control (WorldCat, 
> NLNZ, Wikipedia, etc) for the work. Wise catalogers will use multiple 
> of these URLs and they be used to crosswalk these authorities.
> Claudia Orange publishes a print reference book called "The Treaty of 
> Waitangi" about the constitutional document. Catalogers have no 
> problem describing that this reference work is about the 
> constitutional document, using any of the URLs for the constitutional 
> document as a subject works fine. The print book goes into the queue 
> for cataloging in the national bibliography.
> Several journals publish book reviews. Some of these are digital-only 
> with turnaround times measured in days or weeks. Many of these review 
> the book in an article with the same name as book being reviewed.
> The journal vendors need to produce metadata for these book review 
> articles. Describing the work being reviewed is challenging because:
> (*) we now have three identically-named abstract works by three 
> separate authors
> (*) the book reviews are being published (and largely consumed) weeks 
> or days after the publication of the print work but the print book can 
> take months or years to get 'properly' cataloged (national 
> bibliography, worldcat, etc. )
> (*) the book and the various book reviews are published by completely 
> independently
> Note 1 In this specific case ISBN can be used for an identifier, but 
> of course (a) that's not linked data and (b) that can't be done for 
> the many related cases where the work doesn't qualify for an ISBN, 
> qualifies but has not been issued with an ISBN or has been issued with 
> multiple ISBNs.
> Note 2 RDF essentially lacks the ability to negate, so there is no way 
> that I know of to say "There is a work called 'Treaty of Waitangi' by 
> Claudia Orange. There is a work called 'Treaty of Waitangi' created in 
> 1840. These two are not the same work." A clear method and requirement 
> for doing that would at least make catching some classes of mistakes 
> easier.
> cheers
> stuart
> --
> I have a new phone number: 04 463 5692
> / 
> <>
> ------------------------------------------------------------------------
> *From:* Bibliographic Framework Transition Initiative Forum 
> <[log in to unmask]> on behalf of Joy Nelson 
> <[log in to unmask]>
> *Sent:* Thursday, 25 February 2016 5:11 a.m.
> *To:* [log in to unmask]
> *Subject:* Re: [BIBFRAME] Things I haven't seen in bibframe
> Stuart
> A large chunk of what you talk about strikes me as a version of what I 
> call "Closed Linked Data".  Data that is accessed through 
> publishers/vendors have very unique requirements and access control 
> issues.  I have seen some bibframe vocabulary that relates to this, 
> but I would imagine this in area ready for exploration.
> As far as separating complex works such as The hitchhikers guide to 
> the galaxy, I'm not sure exactly where the confusion lies in your 
> existing catalog.  Although I will say that is my issue with many 
> catalogs--too many records for a few things, some relate and some are 
> separate.  But in a bibframe or linked data world, you would have (for 
> example) 2 URIs for The hitchhikers guide to the galaxy.  One for the 
> book and another for the movie.   The annotations (i.e. reviews) would 
> be their own URI tied to either the URI for the book or the movie - 
> whichever was appropriate.
> I'm not sure this explains it well as I may not have had a great 
> understanding of your initial concern here. I would encourage you to 
> play with the BF tools on the LOC site.  Those tools helped me start 
> to see how thing were connected.
> joy
> On Sun, Feb 21, 2016 at 3:02 PM, Stuart Yeates 
> <[log in to unmask] <mailto:[log in to unmask]>> wrote:
>     I attended the recent bibframe talk given by Kevin Ford at the
>     NLNZ where in the question time and discussion afterwards we had
>     some robust conversations which were limited by the time available.
>     What it seemed to boil down to was my perception that all of the
>     bibframe work I'd seen centered on monograph-like works and
>     pre-digital methods of acquiring and holding bibliographic works
>     rather than the much more complex kinds of works, acquisition and
>     holding currently in use.
>     Kevin's suggestion was that I post to the list with my concerns.
>     Thus this post, which attempts to capture some of the things I've
>     not seen in bibframe (which doesn't necessarily mean that they
>     haven't been done, I'll admit I've not been following the list as
>     I might recently). It reflects only me and my thoughts, not my
>     institution.
>     Journals
>     As an academic library, we purchase many academic journals as
>     packages. Each package is associated with a license. Each package
>     contains one or more date-ranges of one or more journals. Each
>     journal may be digitised for some date ranges and born-digital for
>     others. Each journal date range consists of a number of issues.
>     Each issue consists of a number of articles. Journals which are
>     peer-reviewed contain at least some peer-reviewed articles, but
>     may also contain bibliographically and academically important
>     non-peer reviewed articles (i.e.
>     ) and retractions. Many journals also expose internal metadata
>     (dates of submission, etc).
>     Packages are purchased from vendors and held on platforms. Vendors
>     may subsume one another. Platforms may merge, split or collapse.
>     Platforms may vanish, systematically breaking links (as
> appears to have done). For some date
>     ranges of some journals we have third party preservation
>     arrangements ( Platforms may require
>     access mechanisms (IP addresses, complex proxy stanzas
>     (
>     <>).
>     Content on some platforms is available end-to-end over
>     privacy-preserving HTTPS connections, other platforms use some
>     HTTPS but HTTP for doi resolution, some use pure HTTP. Platforms
>     may or may not have various interoperable methods for statistics
>     gathering ( etc).
>     Platforms have various policies and capabilities for having their
>     content exposed to and reused by third parties and tools acting on
>     our behalf, for example discovery systems to harvest full text,
>     citation counters and journal rankers, etc.
>     That's a stack of complexity, particularly considering I've left
>     out some purely internal dimensions (funding streams,
>     institutional restructuring, audit trails, exchange rate tracking,
>     etc).
>     Patron-driven acquisition
>     Patron-driven acquisition involves us surfacing digital titles we
>     don't own as search results to our users and then purchasing those
>     titles when a user makes a certain amount of use of the title
>     (first access, first N pages, etc, etc).  Patron-driven
>     acquisition is important because it breaks the implicit assumption
>     that records in our library catalog are the records of 'our'
>     holdings. Due to patron driven acquisition, we handle and ingest
>     many more bibliographic items that we are likely to 'hold' in a
>     traditional sense.
>     Certain vendors are giving presentations which portray this as an
>     existential crisis for "The Catalog". While they are of course
>     completely, utterly wrong, initiatives such as bibframe silently
>     ignoring things such as PDA isn't helping dampen the flames of
>     speculation.
>     Authority control
>     Authority control for people is has been discussed for bibframe
>     (mainly VIAF and <>). Authority control
>     for is broader than that, however, and almost certainly needs to
>     be done for serials and probably individual works.
> is a list
>     of apparent attempts to profit (directly or indirectly) from the
>     current confusion in naming academic journals. Proper authority
>     control is the only solution I can see to this.
>     It's also not clear to me how to separate complex works, For
>     example the consider the multiple works known as  "The hitchhikers
>     guide to the galaxy" or "The Tales of Beedle the Bard". This is
>     related to an ongoing issue we have in our discovery system: where
>     a (book/film) review and the work being reviewed have the same
>     name, endless confusion ensues. I'm assuming that authority
>     control would be used to do this kind of disambiguation, but a
>     concrete example would be very useful.
>     I hope this helps.
>     cheers
>     stuart
>     --
>     I have a new phone number: 04 463 5692
> /
> -- 
> Joy Nelson
> Director of Migrations
> ByWater Solutions <>
> Support and Consulting for Open Source Software
> Office: Fort Worth, TX
> Phone/Fax (888)900-8944
> What is Koha? <>

Karen Coyle
[log in to unmask]
m: +1-510-435-8234
skype: kcoylenet/+1-510-984-3600