Thanks for the speedy (and logical) answer.
- Now, if you have records that have employed relators codes, rest
assured that any names with relators codes like "cre" or "aut" will be
associated with the Work. Is that the case?
We've only converted a few records so far but will be focusing on our
RDA cataloging. We should have a fairly extensive set of RDA
bibliographic records in all formats. At the start of our RDA work we
made the decision to add relationship designators to all entities in the
bibliographic records whenever humanly possible. It would be an
interesting project for us to see if they could help map an entity to
the Work or Instance.
I have to admit that the division is not always clear to me, though.
We've already mentioned performed music as an example but drama would
fit in here as well. I'm also interested in BIBFRAME as a possible
model for integrating all the knowledge Stanford produces, not just bib
data. I see strong parallels between a theater or musical performance,
a football game, and a scientific dataset. There is a set of rules (a
musical score, rules of the game, methods), a set of performers
(musicians, football players, physical parts of the experiment) and the
results (a performance, last Monday nights football game, a dataset).
You may have annotations on any part of these (the Friday night
performance of a particular revival (yet again) of Annie), a particular
dataset, etc.). What's the work here? I feel like it's just out of my
reach. Using MARC, I had no hope of even attempting to approach these
issues. I'm hoping in someway BIBFRAME will give me an model I can use
more systematically to resources in general.
>> -----Original Message-----
>> From: Philip Schreur [mailto:[log in to unmask]]
>> Sent: Friday, December 07, 2012 4:55 PM
>> To: Bibliographic Framework Transition Initiative Forum
>> Cc: Ford, Kevin
>> Subject: Re: [BIBFRAME] Early Experimentation Code Available
>> Thanks so much for making this available! Since we've been cataloging
>> in RDA from when testing began, it'll be fun to take all of the records
>> and do a conversion. One question, how would you like
>> comments/questions sent in? For instance (we used the XQuery version),
>> the 700s for additional authors are being attached to the Instance not
>> the Work. In our first example, they were compilers and I thought
>> there may have been some confusion there but in the second they were
>> just straightforward authors.
>> On 12/7/2012 7:04 AM, Ford, Kevin wrote:
>>> We're making code available that will permit programmers and
>> developers to better understand how MARC Bibliographic records can
>> transform to BIBFRAME resources. The code is available at:
>>> There are two versions: one in Python and one in XQuery. The Python
>> version produces JSON files for viewing in a Simile Exhibit
>> presentation (also included). The XQuery version outputs RDF (as
>> RDF/XML, N-triples, or JSON). Although the Python code expects to be
>> invoked from the command line, the XQuery code can be invoked using
>> Oxygen XML or the Eclipse IDE, in addition to a few other methods.
>>> The XQuery is the product of Network Development and MARC Standards
>> staff at LC; the Python version is the work of Zepheira. The two
>> transformations were developed independently of each other. They
>> therefore do not "split" MARC Bibliographic records into BIBFRAME Works,
>> Instances, Authorities, and Annotations in the exact same way.
>>> Both are subject to change. Neither is canonical. They are very
>> much works in progress. As such, the names of properties and
>> classes/entities are in flux and will invariably change in many cases.
>> Sometimes, developers just need to do something to keep going, even if
>> it is subject to alteration later (and often is modified).
>> Nevertheless, we want to make these available for evaluation and to
>> stimulate further conversation.
>>> We are presently working on a way to better expose the output of
>> these transformations to a wider audience. In the next several weeks,
>> we hope to provide a service that will permit individuals to submit
>> their own batch of MARC Bibliographic records for transformation. This
>> way, you can see what *your* data might look like conforming to the
>> BIBFRAME model.
>>> Kevin Ford
>>> Network Development and MARC Standards Office Library of Congress
>>> Washington, DC
>> Philip E. Schreur
>> Head, Metadata Department
>> Stanford University
>> 650-725-1120 (fax)