PIDfest 26

More PIDs in More Places: Better Data and Interfaces
2026-10-27 , LUMC01

In this session you'll learn how and why Stanford University is integrating more PIDs throughout its research infrastructure. You'll learn about the rationale for the paths we've chosen and the benefits we've seen from these projects, and we'll discuss the challenges we've encountered and the work we have yet to do. You'll hear about three case studies utilizing three different PIDs: ORCID iDs, DOIs, and the newest PID -- BIBFRAME URIs via Blue Core.


In this session you'll learn how and why Stanford University is integrating more PIDs throughout its research infrastructure. You may recognize from your own institutions the decentralized nature of many of these efforts, which we've pieced together into an integrated set of PID-powered services. You'll learn about the rationale for the paths we've chosen, the benefits we've seen, the challenges we've encountered, and the work we have yet to do. We'll focus on three case studies from our work that highlight ORCID iDs, DOIs, and a new PID for bibliographic description.

Our first case study shows how our authorize.stanford.edu service allows researchers to connect their ORCID iD to their university credentials and authorizes Stanford to push information to ORCID records. This service is the hub for a web of interconnections among our institutional researcher information system, Stanford Profiles, and the Stanford Digital Repository (SDR). ORCID iDs are included in both Profiles and SDR records and from these sources we push article publication information and published datasets and code to ORCID records. Over time we've improved ORCID entry options in our SDR campus deposit application; these improvements streamline the user experience and improve the metadata. However, we have more work to do so that our ORCID options work equally well for all authors and records make the full circle back to the Profiles system.

In our second case study, you'll learn about our new easier workflow for depositing manuscripts into the SDR utilizing existing DOI metadata, which was prompted by the recommendation of a Stanford faculty committee reviewing the Open Access Policy. You'll see how our latest SDR deposit workflow, developed in response to this recommendation, simplifies the process by retrieving key metadata including ORCID iDs and RORs from the DOI for published work. However, not all articles have a DOI (or have one yet), and not all DOI metadata is as complete as we would like. You'll hear how we are using AI on a small scale to assist with this process when needed, and how we plan to address these challenges in the future by extending AI use and providing COMET-style enhancements to both DOI and ORCID metadata.

In our last case study, you'll hear about Blue Core URIs as persistent identifiers and about our multi-year project to move to BIBFRAME, a linked open data successor to MARC for bibliographic description. Blue Core seeks to build a common set of linked open data URIs for BIBFRAME so that institutions can collaboratively create catalog "records" in a shared, authoritative pool of data. This model embraces a global network of catalog metadata, with Blue Core URIs serving as PIDs. Blue Core includes a data store and API, and like other PIDs, includes a URI with associated metadata for querying and reuse. A collaborative editing environment will ensure that all institutions benefit from the most comprehensive data pool and continuous updates.

Science Data Librarian, Stanford University Libraries

Peter Mangiafico is a software engineer and product manager in Digital Library Systems and Services in Stanford University Libraries. Peter works on a number of projects, including the Stanford Digital Repository (SDR) and RIALTO (a research intelligence system). Before Stanford, he worked on projects with Visionlearning, the Marine Biological Lab in Woods Hole, MA, Harvard University, and the Advent of Complex Life NASA Astrobiology team. He worked for several years on the Encyclopedia of Life project, and has previously worked as a software engineer, project manager, high school teacher, and NASA researcher.