Workshop slides presented to a group at the University of Hawaii, December 4, 2014. Slides include a step-by-step description of importing a MARC file to RIMMF, plus some issues that remain after the process and products are examined.
Handling a related resource: first found in Cornell’s Voyager catalog. The available exports don’t include the MARC UTF-8 option.
LOC’s catalog allows a ‘save record’ option that enables export to RIMMF.
The save file option (this is a Mac, remember!) is handled by saving the file to a specified location.
In the downloads folder, the record shows up with a generic name. That record is dropped atop the RIMMF page.
RIMMF will show an r-tree set of records created from that action. Press the ‘import’ button and RIMMF will import the record to the local file.
Arrows: (1) Click on the box and the odd character will disappear. The change to the composite key will flow through the related records. (2) Note how the LCCN and ISBN are handled. (3) Note that the extent ‘statement’ is drawn from the MARC record, and then parsed into the number of units and type of units for better machine readability. (4) Note that the link to the expression is added automatically.
Source consulted is not particularly helpful (it is really metadata about metadata), and JSC is considering how to handle it in the WEMI context.
The work aggregation also includes ‘source consulted’ –feel free to delete. Note that JSC is considering the issue of subjects, no conclusion yet.
Author is added to the related sense and sensibility record—automated process cascades that through the related elements.
RIMMF adds the related works (two here) to the r-tree for the S&S work.
This slide and those following reflect some issues with RDF data in a RIMMF context, as well as general issues and relevant questions.
Playing with Jane
A step-by-step introduction to describing the
resources swirling around Jane Austin
University of Hawaii, December 2014
Well constructed for FRBR-based description
Data structure comes from RDA Registry
Links to RDA Toolkit throughout data building
Useful visualization of groups of records
Improves discussion of issues with RDA
Step-by-step illustration of adding a record [next]
Playing with Jane, Hawaii, 12/2014 2
Issues for Discussion
Looking more clearly at workflow and maintenance
Provenance: who, what when, [where?]
Playing with Jane, Hawaii, 12/2014 13
Substituting a Cache for
Supports multiple streams of data
Allows detailed provenance to be carried over time
Separates services from data storage
Allows more extensive automation (and
orchestration of services)
Focuses valuable human effort where it’s needed:
analysis, design and implementation of
Playing with Jane, Hawaii, 12/2014 14
Obtain data (possibly as ‘records’)
Store data as statements in cache
Evaluate data by source or collection
Improve data using specific services, as determined
Publish improved data
Playing with Jane, Hawaii, 12/2014 15
Rule: Use humans for things requiring human
understanding and decision making
Use machines for everything else
A manual process for something a machine can do as
well or better is a failure
Improvement services can be granular, invoked in
prescribed order, and report results for later use
Continuous improvement necessary to respond to
Playing with Jane, Hawaii, 12/2014 16
• Improved data returns as statements to the data cache,
with provenance attached
• Statement strategy avoids overwriting of new data over
Each new statement adds to what is known about a
Statements can be cherry picked and exposed to others in
statements or records, in ‘flavors’ or as a ‘everything we
Playing with Jane, Hawaii, 12/2014 17
The First MetadataMobile
Playing with Jane, Hawaii, 12/2014 18