I did, and I'm in the process of installing what I need. But by
documentation I think: not just for people running the program, but
documentation about what the program DOES. What MARC fields does it
transform into BIBFRAME fields? How are those decisions made? What are
the goals? The program is the HOW but we need the WHAT and the WHY --
not the least because it takes longer to install a program and run a
bunch of tests than to read some documentation. And not everyone CAN
install the program and run a bunch of tests. And it isn't efficient for
us all to be installing programs and running tests.
On 12/7/12 10:02 AM, Morgan V. Cundiff wrote:
> Take a look at the readme files:
> On Fri, 7 Dec 2012, Karen Coyle wrote:
>> Dare I ask: documentation? Please? And maybe a few examples of
>> On 12/7/12 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
>> Karen Coyle
>> [log in to unmask] http://kcoyle.net
>> ph: 1-510-540-7596
>> m: 1-510-435-8234
>> skype: kcoylenet
[log in to unmask] http://kcoyle.net