Page History

LD4P began as tool for the transformation of library metadata production from workflows based in the MARC formats to linked data. As the project evolves, however, it becomes an opportunity to reevaluate the library’s role in a developing, worldwide information ecosystem.

While much of the world knows about Wikipedia, the emergence of Wikidata as a key global structured data project has only recently emerged as a key way to engage libraries, archives and museums. Andrew will discuss the ways in which the Wikimedia movement has adopted Wikidata and how it interfaces to institutions and collections through linked open data initiatives and innovative reuse. He will talk about notable projects that showcase these and a vision for the future which includes projects such as Structured Data on (Wikimedia) Commons, a global citation database in WikiCite and unified collections contributions workflows now being engineered tougher by the Wikimedia community and GLAM institutions.

Through considering a case study written for the Design for Diversity project, we will consider how metadata and aggregation across collections has simultaneous potentials: to perhaps surface a more diverse range of histories and cultures; to perhaps surface those histories but through metadata that still lacks cultural relevance or respect; or to perhaps only re-inscribe the largely white, largely male histories represented in U.S. library, archive, and museum collections. Amanda Rust will first briefly introduce the Design for Diversity project, and Dorothy Berry will then discuss her work making African American materials more discoverable through digitization and metadata aggregation in Umbra Search.

Tom Cramer, Jessie Keck, Huda Khan, Dan Scott, and Simeon Warner on knowledge panels.

This presentation explores the intersection of philosophical theories of time and their experimental serializations in RDF and related languages. Implications for adoption of particular models is addressed as well as future areas for exploration.

We consider rich semantics beyond typical approaches to linked data. For instance, we have explored supporting access to the NEH/LC NDNP digitized historical newspaper collection. Retrieval with dynamic, structured “community models” seems more promising than traditional indexing. We also applied rich semantic modeling to scientific research reports so that they would be implemented as knowledgebases rather than as text. Upper ontologies, frame semantics, and object-oriented programming-language semantics are among the approaches that may be incorporated into such “direct representation".

This presentations describes a six-month project to build an intermediate knowledge layer between a knowledge base of classical texts built using FRBRoo and the CITE architecture and the Perseus catalog of published works. The process entailed automatic extraction of works and expressions from multiple MODS records and their recombination into FRBRoo statements, which were then made available through a SPARQL endpoint.

UC San Diego's participation in the LD4P2 Cohort will revolve around describing Open Access (OA) resources. This presentation will cover some of the driving forces behind this focus on Open Access materials, the opportunities and challenges we see for describing them with the BIBFRAME model, and our current training and preparation for the release of the Sinopia editor.

The Wikidata Tutorial will provide a hands-on introduction to the basics of Wikidata and the Wikidata Query Tool. Participants will learn the basic functions of both and how to make simple manual edits to Wikidata items and create simply database queries. The workshop will also discuss how institutions can use Wikidata effectively and employ automated tools like the Distributed Game and OpenRefine. A laptop or mobile device will be necessary to fully participate in the workshop.

For those with a basic understanding of the design and organization of Wikidata items, this session introduces the best practices for working with collections of data and their associated ontologies. Ideally, attendees will bring a laptop device to better experiment and try out the tools introduced, but a mobile device can also suffice.The session will cover key tools for discovering, uploading, fixing and reusing Wikidata content for collections, and include notable case studies with GLAM institutions such as the Smithsonian Institution and The Metropolitan Museum of Art.

Tools to be covered include:

• Wikidata user-selectable gadgets such as Recoin, EasyQuery and Hotcat.
• WikiProjects that 
• SQID for browsing Wikidata entity relationships
• Wikidata Query advanced methods
• Wikidata Graph Builder for investigating ontologies
• TABernacle for editing and fixing collections data
• Quickstatements for buik uploading and item modification
• Wikidata Game for mobile-friend crowdsourced Wikidata contributions and fixes
• Petscan for advanced querying across Wikimedia projects
• PAWS and Python tools for advanced scripting and needs

From MARC to BIBFRAME and back again

The Library of Congress must convert its existing MARC data to BIBFRAME in order to migrate to BIBFRAME. What has always been recognized as equally necessary, but has otherwise been far less prominent, is the need to convert BIBFRAME data back into MARC.

There are numerous reasons the Library of Congress must do this. After full adoption, LC must still distribute MARC records as part of its distribution service until such time there is no longer serious demand. LC’s Voyager system, including the OPAC, is MARC-based, and there are innumerable other systems at LC that not only expect but might only be able to consume MARC data. These realities therefore means that LC will need to convert MARC records to BIBFRAME and then back into MARC, either for system consumption and/or distribution.

These scenarios raise countless questions: How will more or less granular data be converted? Do we have the data and/or mapping to reconstruct a MARC 008 and 007 fields, or Leader? How do we merge Works and Instances back into a MARC record? Can we faithfully reconstitute a MARC record based on given LCCN? What is the future role of the LCCN in this environment?
This session will describe how LC is addressing some of these questions as well as demonstrate some concrete steps to being able to do this.

Issues around building a system to house and test BIBFRAME data

The presentation will deal with major topics such as issues relating to ingesting converted descriptions and linking them properly, dealing with the differences between editor content and conversion content, and identifiers when URIs do not exist.Nate Trail. LC BIBFRAME System Notes: Build the Plane while flying
Kevin Ford. Anonymous Resource* Wrangling at LC (*a.k.a Blank Node)
Sally McCallum. MARC and BIBFRAME
Matt Miller. LC BIBFRAME Editor Updates

This is a pilot project the USF Libraries Linked Data Team has done to experiment transforming the digital collections into linked data. The Team chose a small oral history collection to work on and the team was able to reconcile the data, transform the data into triples and design SPARQL queries to support basic search. Throughout the process, the Team was inspired to streamline the workflow and further enhance the final product.

A case study of introducing linked data concepts to a cataloging request and the successful partnership between cataloging and a campus data archive.

• If you are cataloging materials in a linked data editor, does your institution plan to represent those materials in the current integrated library system, or other local systems?
• Is it best practice to continue to manage a MARC dataset alongside RDF entities or other linked data datasets? Or, will it be best to transform historic data so that bibliographic data is uniformly represented in a local system? What are the risks and benefits associated with each of the options?
• What are the functional requirements for managing linked data for description in a system such as FOLIO that is intended to be format agnostic for bibliographic data?