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.

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.

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.

Stanford implemented Schema.org in its Blacklight-based catalog SearchWorks. This lightning talk will discuss the implementation, plans for enhancements, and the path forward to shareability with other Blacklight-based discovery environments.

Learn how bibliographic data provided by libraries is used at Google and why machine-readable linked data is the way to go.

I will describe my attempt so far, to learn what linked data is and to implement a simplified project at my institution. I use my university’s strategic goals to convince our administration and colleagues and I want to inspire them with a demonstration showing the results of higher visibility of a unique collection to benefit anyone interested in this collection.

A visual workflow not only helps students and volunteers with cataloging, but also supports Linked Data with a focus on concepts instead of terms. The worksheet tool at DressDiscover.org explores this approach for describing artifacts of historic clothing, providing visual choices backed by terms from thesauri that are available as linked data.

One of the chief promises of linked data for libraries is search engine visibility. Few studies, however, have attempted a quantitative analysis of linked data's impact on search engine rankings. This presentation will review a linked data project from a search engine optimization perspective.

eagle-i (www.eagle-i.net) is an open platform, open ontology discovery tool for research resources, including microscopes, equipment, stem cells, transgenic mice, and software. It is a distributed node network of 40 institutions linked by a central search. For ten years, it has been a stable resource but has been somewhat forgotten. As science and research have moved to a more open model, what role can eagle-I play, and how can the linked data that describes the resources be used in the research and publishing cycles? This presentation shares answers to these questions.

This session will not be recorded.

In this hands-on workshop (using the sandbox at https://omeka.org/s/download/#sandbox) we will begin with a brief introduction to the popular digital humanities publication platform Omeka S and how it implements Linked Open Data. We will focus on content creation and, of course, metadata creation options using a variety of LOD vocabularies, and how content and metadata are represented in the JSON-LD-based API. To get the most out of this tutorial, participants should bring a laptop and have access to a few files (images or other content) and some metadata for those files.

This session is about the story of the National Archives' first catalog API—our design choices, use cases, philosophies—and how it has evolved over 5 years of development and use, and become engrained in our daily work. It is a story not just about the API itself, but how the act of designing an API from scratch has provoked us to change old ways of thinking about discovery, reference, and, ultimately, archival work itself.

This lightning talk will discuss the Perseus Catalog, a research project of the Perseus Digital Library, and current work to convert the legacy metadata collection and related bibliographic data to linked data standards.

Starting in 2018 as part of the Cultivating a Latin American Post-Custodial Archival Praxis grant funded by the Andrew W. Mellon Foundation, the LLILAS Benson Post Custodial project team began working on developing and migrating the Latin American Digital Initiatives (LADI) digital repository to the Drupal 8/Islandora 8 (formerly CLAW)/Fedora 4 repository framework. One core component of this work includes investigations and implementation of linked data capabilities for better discoverability, access, and analysis.

Implementation of BIBFRAME or other linked data cataloging workflows at scale will require institutions to address both how the data will be managed over time and how administrative activities that have been driven by MARC data will need to adapt. Bring your ideas, concerns, and questions to this conversation about what is necessary in the short-term as we experiment with new approaches to description and what is required in the long-term to make adoption of best practices feasible. Potential discussion questions include:

• 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?