A Lightweight Structured Data Implementation Using JSONLD and

  • Slides: 15
Download presentation
A Lightweight Structured Data Implementation Using JSON-LD and Schema. org for Digital Repository Lucas

A Lightweight Structured Data Implementation Using JSON-LD and Schema. org for Digital Repository Lucas Mak, Lisa Lorenzo, Nicole Smeltekop Michigan State University Libraries ALCTS Ca. MMS Cataloging Norms Interest Group (ALA Midwinter 2017, Atlanta GA, January 21, 2017)

Background • Digital repository @ MSU • Islandora repository • Formats • Text, audio,

Background • Digital repository @ MSU • Islandora repository • Formats • Text, audio, image, compound object • Metadata • Marc. XML, MODS, DC, ETD-MS • Stored as datastreams along with digital objects

Structured Data Markup • “Describes things on the Web with their properties”* • Typically

Structured Data Markup • “Describes things on the Web with their properties”* • Typically uses schema. org vocabulary • Commonly in JSON-LD, RDFa, or microdata format

What others have done …

What others have done …

What we want …

What we want …

Mapping

Mapping

Choosing Markup Format

Choosing Markup Format

Validation Google Structured Data Testing Tool @ https: //search. google. com/structured-data/testing-tool? url

Validation Google Structured Data Testing Tool @ https: //search. google. com/structured-data/testing-tool? url

Creating Transformation </> XSLT

Creating Transformation </> XSLT

Implementation MODS JSON-LD XSLT

Implementation MODS JSON-LD XSLT

Getting URIs into JSON-LD • Getting URIs into source data • URIs inserted by

Getting URIs into JSON-LD • Getting URIs into source data • URIs inserted by authority vendor during authority processing (for records originated from the catalog) • Inserts URIs into $0 in Marc. XML or @value. URI in MODS manually or programmatically using conversion table • Possibly using Marc. Next in Marc. Edit or querying APIs of various linked data services in the future • Builds URIs for certain elements during transformation from Marc. XML to MODS • e. g. Language code: eng http: //id. loc. gov/vocabulary/iso 639 -2/eng • URIs in MODS get carried over to JSON-LD during XSLT transformation

Getting URIs into JSON-LD • LCSH – the sticking point • Not all possible

Getting URIs into JSON-LD • LCSH – the sticking point • Not all possible LCSH strings have corresponding URIs • Holocaust memorials http: //id. loc. gov/authorities/subjects/sh 88005153 • Poland http: //id. loc. gov/authorities/names/n 79131071 • Holocaust memorials -- Poland ? ? • Pattern headings • Personal narratives, American, [French, etc. ] http: //id. loc. gov/authorities/subjects/sh 99001715 • Can we really use this URI? • FAST – the “solution” • Holocaust memorials http: //id. worldcat. org/fast/958834 • Poland http: //id. worldcat. org/fast/1206891 • Personal narratives--American http: //id. worldcat. org/fast/1424071

Getting URIs into JSON-LD • FAST – the “solution” • Gets FAST headings and

Getting URIs into JSON-LD • FAST – the “solution” • Gets FAST headings and IDs from LCSH using OCLC FAST Converter • Builds URIs based on FAST ID inserted in $0 during transformation into MODS e. g. World War (1939 -1945) (OCo. LC)fst 01180924 http: //id. worldcat. org/fast/1180924 • Problem: Lag in update of the converter database @ https: //fast. oclc. org/lcsh 2 fast/

Next Step • Script to convert LCSH in MODS to FAST using OCLC FAST

Next Step • Script to convert LCSH in MODS to FAST using OCLC FAST API • Marc. XML not available for all digital collections • Moving away from creating Marc. XML • Should we just use FAST? ? • Markup in vocabularies other than schema. org, e. g. dcterms

Thank You! Lucas Mak makw@mail. lib. msu. edu Lisa Lorenzo lorenzo 7@mail. lib. msu.

Thank You! Lucas Mak makw@mail. lib. msu. edu Lisa Lorenzo lorenzo 7@mail. lib. msu. edu Nicole Smeltekop nicole@mail. lib. msu. edu