Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Publishing Aleph records as LOD

C7edab8d350fffad9fa06e2de9d4e885?s=47 lobid
September 30, 2013

Publishing Aleph records as LOD

Presentation held by Adrian Pohl and Pascal Christoph on 2013-09-30 in WebEx of IGELU/ELUNA Special Interest Working Group on Linked Open Data with Ex Libris representatives.

C7edab8d350fffad9fa06e2de9d4e885?s=128

lobid

September 30, 2013
Tweet

Transcript

  1. Publishing Aleph records as LOD IGELU/ELUNA-Ex Libris LOD SIWG call,

    2013-09-30 Pascal Christoph & Adrian Pohl
  2. Background 2 Christoph/Pohl: Publishing Aleph records as LOD hbz runs

    a union catalog on Aleph since 1999 Currently 18 M records with holdings Publishing LOD via lobid.org since 2010 Primary goal: web-integrated data for discoverability and re-usability
  3. Publishing LOD from Aleph 3 Local development for exporting daily

    updates Converting Aleph XML to RDF with Metafacture Vocabularies used: DC, Bibo, FRBR core, isbd, marcrel, lobid-vocab, foaf (see list here) LOD exposed in different ways: HTML/RDFa and content negotiation via lobid.org Full dumps: http://datahub.io/dataset/lobid-resources Triple store with SPARQL endpoint Web-API: http://api.lobid.org Christoph/Pohl: Publishing Aleph records as LOD
  4. lobid API 4 Enables powerful reuse options of LOD, e.g.:

    Mash-Ups Auto-suggest for cataloging and searching lobid.org frontend will soon run on the lobid API (until now based on triple store) API complemented by data dumps & SPARQL endpoint Also exposed via API: authority data from ISIL registries & German Integrated Auhtority File Christoph/Pohl: Publishing Aleph records as LOD
  5. Technology stack 5 Christoph/Pohl: Publishing Aleph records as LOD

  6. Live demonstration 6 http://api.lobid.org Christoph/Pohl: Publishing Aleph records as LOD

  7. Outlook 7 Switch lobid.org to API backend Add more data

    from GND Integrate data from Cultural Heritage Organizations vocabulary Implement the web & search interface for the North Rhine-Westphalian Bibliography based on the lobid API Christoph/Pohl: Publishing Aleph records as LOD
  8. What should Ex Libris do? 8 Provide interfaces for legacy

    and future systems Push interface (event driven => real time) Use open standards for interfaces Interfaces not limited to catalog data but for all data (e.g. statistics, user data) in open formats Christoph/Pohl: Publishing Aleph records as LOD
  9. Thanks. Questions? With pleasure now or later to semweb@hbz-nrw.de or

    @lobidOrg 9
  10. Further information 10 Use case description: http://www.exlibrisgroup.org/x/cww5Ag hbz LOD blog:

    https://wiki1.hbz-nrw.de/pages/viewrecentblogposts.action?key=SEM lobid API documentation: http://api.lobid.org lobid code & issues: https://github.com/lobid/ Metafacture code: https://github.com/culturegraph/metafacture-core Metafacture Blogpost by Fabian Steeg: Metadata processing with Metafacture and Eclipse. URL: http://wp.me/pwKJk-oN Christoph, Pascal: Building a High Performance Environment for RDF Publishing. Talk at SWIB12. Slides at http://swib.org/swib12/slides/Christoph_SWIB12_117.pdf, video at http://www.scivee.tv/node/55329. Ostrowski, Felix / Pohl, Adrian (2012): Towards an Editable, Versionized LOD Service for Library Data. In: LIBER Quarterly 22 (2013), Nr. 4, S. 310-330, URN: URN:NBN:NL:UI:10-1-114290 (This article is about the prior SPARQL/Fresnel-based implementation of lobid.org implemented with the self-developed software Phresnel.) Christoph/Pohl: Publishing Aleph records as LOD
  11. License 11 Christoph/Pohl: Publishing Aleph records as LOD These slides

    are published under a Creative Commons license: http://creativecommons.org/licenses/by/3.0/de/