PREFIX schema: <http://schema.org/>
SELECT ?fastURI ?fastHeading
?s schema:about ?fastURI .
?fastURI schema:name ?fastHeading
FILTER regex(str(?fastURI), 'http://id.worldcat.org/fast/')
Just hack the number in the query.
There may be a throttle on the request rate, but in principle this Linked Data solution could help.
Here’s a link (http://bit.ly/1NR0rVa) to very short presentation I gave at a LD4L workshop about adding URI’s in $0’s. It focuses on a pilot to add VIVO URI’s for Cornell faculty to 700’s in MARC bib records for theses where the faculty serve as advisors. It also discusses our interest in using WorldCat Work URIs. I’ve provided screenshots in the presentation of URI’s in Stanford’s authorities and George Washington’s bibs; I came to know of these efforts from attending the following session at DCMI2014, http://dcevents.dublincore.org/IntConf/dc-2014/paper/view/314. Slides are available, including Peter Green and Tim Thompson’s presentation on Princeton’s work.
In LD4L we’re investigating pre and post-processing steps in our MARC and non-MARC to BIBFRAME and other RDF conversions that include reconciliation with VIAF, id.loc.gov, Getty Vocabs and more. For more on the LD4L Workshop, check out https://wiki.duraspace.org/display/ld4l/LD4L+Workshop+Overview
Cornell Technical Services has also collaborated with OCLC to add FAST headings to all of our bibs that have LCSH; to be clear… we’re retaining our LCSH while adding the FAST equivalent. We’re very close to using these headings in our production catalog. With the addition of FAST we’re getting a $0 control number (not the dereferenceable URI) for the heading. It won’t be hard to create the URI when we convert to RDF. Here’s an example of a record with the FAST, https://newcatalog.library.cornell.edu/catalog/7383096/librarian_view
Hope this helps.
Discovery Metadata Librarian
Cornell University Library
On 4/4/15, 5:22 PM, "Peter Green" <[log in to unmask]> wrote:
We're currently sketching out the process and scripts for adding $0 to
our (existing) Voyager records in bulk, having already done some
proof-of-concept testing, and will be eager to share our discoveries.
"We" is pretty much just Tech. Services staff, by the way, so we are /
will be learning quite a lot.
Speaking of steps that can be taken now: Has anyone incorporated the
MarcEdit Link Identifiers tool into their cataloging workflows? If so, how?
On 04/04/2015 04:07 PM, Karen Coyle wrote:
On 4/4/15 12:27 PM, Steven Folsom wrote:
Yes, we will be working with MARC for a while longer. I, too, hope in
the meantime that we make strides in sanctioned additions and work
arounds to MARC that position us for better days, e.g. more $0 URI’s
that are dereferenceable.
Just want to note that some of the same vendors who do authority
updates will also add the appropriate URI in the $0 of the returned
record. I've been told, however, that this service is not being
requested by customers. Getting those $0's filled in would make it
possible for all library systems to produce useful schema.org markup
in their displays. It would also make any conversion to BIBFRAME or
RDA in RDF much more economical because the identifiers would already
So, is anyone doing this? Getting the $0's filled in? Do you have info
to report from your experience?