So annotations are where stuff gets interesting – annotations are the place to put all that contextual knowledge that librarians, collection managers, information users, intellectual content creators – have, related to information resources. Those relationships that are too messy and squishy to fit expressed by FRBR and fit into MARC
1) Eric Miller gives uplifting talks about the values of making these connections – this is an Example stolen from Eric Miller – Great Gatsby, with original dust jacket art based on a painting by Francis Cugat, “Celestial eyes” (Smithsonian article from last year) on the occasion of this exhibition at Princeton, where
2) I guess the original painting is, because they have the Scribner family archives. Whole long story about how a Scribner cousin found the painting in a trash can, liked it, took it home, it was passed it down through the family for a generation or two, and ended up at Princeton because Charles Scribner III is class of 1973 at Princeton, and “kindly donated it to Princeton”
3) Really really wanted to find a MARC record with a note that said original dust jacket by Francis Cugat. So tried at Princeton, and couldn’t find it – remembered that the photo the credit for that Smithsonian article said USC - tried there – and look, right cover – BUT but this is a 2004 reprint.
4)So tried limiting to special collections, and got this – some lovely notes related to the provenace of this copy – but nothing about the cover – and a note that it’s in a descriptive bibliography of Gatsbys
5) Tried the LCCN in worldcat – and here’s what I got – sans the local notes, descriptive bibliography note – nothing about Cugat. Cugat & Fiztgerald keyword searched in WorldCat got me a tote bag; Cugat and Gatsby in Google got me the record for the Hathi Trust digitized copy – and that was even more frustrating, because I could see some lines of the forward that mentioned Cugat in my Google hit list, but when I tracked down the Hathi Trust it’s a search only, not even snippet view copy because of copyright
So the potential for making these linkages using BIBFRAME is really attractive!
What does the underlying code look like? At BIBFRAME.org, you can transform MARCXML to BIBFRAME – this is RDF
Note links to subjects
Even though all the annotations are much sexier, the links that are the most developed now are the authority links- like this one to LCNAF for Fitzgerald
So that’s converting existing MARC to BIBFRAME – to create new BIBFRAMR descriptions, BFE – BIBFRAME editor.
This is FAR from an online cataloging tool – as it says here the point is to dowonload the code, and what yu get is a BIBFRAMR cataloging interface that you can adapt for local use.
Here are some points to remember when “playing” with the online Demo: 1) The only templates available to you “out of the box” are holding, instance, work, authority, and “all”. The tool, however, includes all the BF vocabulary properties in support of enabling the selection of subsets (templates) of these large templates, creating new ones for specific uses by catalogers (e.g., minimal description for a book, sheet music). In the code source, the base Profiles are available for your manipulation. 2) There is NO back end storage at this time in the Demo. A completed description is staged for export and saving but until we have added a datastore to the Demo you cannot save your input. It is expected that if you Download you are planning to use the tool with a datastore, which you will need to configure locally and from which you could retrieve descriptions for editing. 3) The left hand column of the input screen lists the templates currently available. These are fully configurable if you download the source code. It is where we plan to add ones from time to time on the Demo. 4) The right side of the input screen lists the resource template(s) and its properties for describing material. 5) A few fields feature a typeahead, or lookup, service. The Demo looks only at the LC’s ID.LOC.GOV at the moment, but with Download developers can create new lookup points, bringing in lists from other Linked Data services. The data is then recorded via a URI to the data. 6) For any label preceding a data box, the definition may be found in the BIBFRAME Vocabulary. 7) If an entity is structured in the BIBFRAME Vocabulary, then click on the data box to bring up a new template for the structured components. 8) The Demo works under a number of browsers (Firefox, Chrome) but not all IE browsers.
If you do decide to play with the demo, another caveat directing you to get the code from github
Here’s the demo, selected profile for for creating new work - If I chose associated agent - person
And started typing Fitzgerald – like I said, links to authorities the most developed.
Schema.org is a way to add structured linked data to html pages, as html tags, directly on the page, so that they make more sense to search engines, and the data displayed can start getting built into google knowledge graphs. Library catalog records are often displayed as web pages, so building scheme.org into web display of catalog records is a step towards EXPOSING library data, getting it into the inked data world – and OCLC is doing this. The Schema.org set of authorized tags was developed for e-commerce – so potentially one avenue for librarians to get more involved is adding to and kind of “authoritizing” those tags – getting more designations that libraries need into schema.org
And in fact, OCLC is has begun this work – extending schema.org
BIBFRAME is a way to actually re-encode MARC in a linked data format – RDF/XML BIBFRAME is still a model – if you look at the FAQs in answer to when do I move to BIBFRAME? “BIBFRAME is far from an environment that you could move to yet. The model and its components are still in discussion and development -- a work in progress. When it is more mature, vendors and suppliers will need time to adjust services to accommodate it. And then we can expect a mixed environment for some time”
Exiting MARC is going to be batch converted to BIBFRAME – I personally don’t see us be doing this by hand! Emphasis on utilizing exiting metadata – no original cataloging except for the unique and local
Linked Data’s Many Forms - BIBFRAME
Many Flavors of Linked Data:
WiLS OCLC Peer Council
June 4, 2014
“Lack of demand, particularly since
many catalogs contain a lot of garbage
metadata and/or resources that others
cannot access. Plus, the information
goes stale quickly. Not that there's no
use for this information, but not that
many people are asking.
Kyle Bannerjee, Digital Collections and Metadata Librarian, OHSU
What is BIBFRAME?
“In addition to being a replacement for MARC,
BIBFRAME serves as a general model for
expressing and connecting bibliographic data.
A major focus of the initiative will be to
determine a transition path for the MARC 21
formats while preserving a robust data
exchange that has supported resource sharing
and cataloging cost savings in recent decades.”
A little history
May 2, 2014 –
• The BIBFRAME Editor (BFE) is a simple tool that
enables input of any BIBFRAME vocabulary
element. The BFE will be frequently improved as
small features are added and user comments
come in. There is a Demo version that you may
directly experiment with. In addition, our primary
purpose for the tool is the open source Download
version of the software that you may take and
integrate into your experimental systems,
enabling many features that the Demo cannot
Schema.org vs. BIBFRAME
• Schema.org way to add html tags to web pages – that can
be displaying bibliographic information
• OCLC is adding schema.org linked data to WorldCat record
• Librarians can add to/authoritize schema.org definitions
• WorldCat Linked Data Vocabulary -
• BIBFRAME way to re-encode MARC in a linked data
• Not ready yet, but best we have so far?
• Existing MARC data can be batch transformed to BIBFRAME
• Editor - BFE for creating new descriptions