This page provides additional details around the integration of information from Wikidata, DbPediaDBPedia, and the Library of Congress (LOC) linked data service into the Cornell production catalog. We began this work as part of LD4P2 and LD4P3 discovery explorations around knowledge panels and author and subject pages. After multiple discussions with our library user representatives and modifications based on their feedback, we coordinated with the Discovery and Access team, the group responsible for our catalog implementation, to move forward with this integration.
...
- Knowledge panels
- We now include an image and short description from Wikidata.
- Author and subject browse pages:
- We now include
- An image from Wikidata
- A description from DbPedia DBPedia (or a description from Wikidata if the former is not available)
- Additional Wikidata information for people such as citizenship, education, and pseudonyms
- The LOC classification number which is used to generate a link to our call number browse.
- We now include
...
All of the data on the page is retrieved using dynamic lookups against external data sources to retrieve information. We also check against our configuration to see which data or authorities should show information from external sources. (This process is described in greater detail below). Currently, the author knowledge panel and author and subject pages rely on a string lookup of the authorized heading string against the id.loc.gov suggest service. This lookup returns a URI which we then use to retrieve LOC information such as the classification number and to query Wikidata. DbPedia DBPedia queries use a combination of Wikidata QID and label searches to retrieve descriptions. Additionally, we have requested the inclusion of LOC identifiers or URIs within the catalog Solr indices and, in the future, we hope to be able to use that information directly instead of relying on string lookups to get LOC URIs .
...
If we did not want to show any of the information we retrieve from Wikidata or DbPedia DBPedia for this specific heading, we would instead write the following in the YAML file:
...