1 / 16

Roxana Popistaşu IT staff Roxana-Maria.Popistasu@bnl.etat.lu

Roxana Popistaşu IT staff Roxana-Maria.Popistasu@bnl.etat.lu. Linked Data: From ALEPH/PRIMO to Autorenlexikon and back. Linked Data. Aleph OPAC. & Primo. Autorenlexikon. Project partners. National Library of Luxembourg Manages ALEPH & PRIMO for the network of libraries in Luxembourg

leecooper
Download Presentation

Roxana Popistaşu IT staff Roxana-Maria.Popistasu@bnl.etat.lu

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Roxana PopistaşuIT staffRoxana-Maria.Popistasu@bnl.etat.lu Linked Data: From ALEPH/PRIMO to Autorenlexikon and back

  2. Linked Data Aleph OPAC & Primo Autorenlexikon

  3. Project partners • National Library of Luxembourg • Manages ALEPH & PRIMO for the network of libraries in Luxembourg • Centre national de littérature • Manages the content of Autorenlexikon • Magic moving pixel • IT management side for Autorenlexikon

  4. The pilot project • November 2012 – January 2013 • Goal: • Analyze the possibility to create links between the authors in ALEPH (bibliographic / authority records) and their corresponding authors in Autorenlexikon. • The analysis determined the best technological choices and the needed manpower.

  5. The pilot project • Questions to be answered: • How to create a link between authors (string matching / id’s)? • How to deal with identical names? • How to deal with the authority records? • How to do find (and save?) the matches? • “on the fly” with the help of web services • “offline” (storing the matches in a DB)

  6. The pilot project • Results: • Low number of matches between Autorenlexikon • and the bibliographic database (~ 60%) • and the authority database (~ 35%) • No ID matching possible => string matching • Prototype for display in the ALEPH catalogue

  7. The pilot project • OPAC prototype

  8. The linking project • Timeline: March 2013 – present (in progress) • Phase 1: March – May 2013 • Adjust matching algorithm • Create database with matches • Create web service to be used for the display in the catalogue and in Autorenlexikon • Display matches in the ALEPH OPAC • Create validation service

  9. The linking project • Adjust the matching algorithm • Normalization rules • Cataloguing rules: ALEPH (MARC21) vs Autorenlexikon • Levels of matching (accuracy) • Create database with matches • Update database automatically and regularly, using as input exports from ALEPH (bibliographic database), respectively Autorenlexikon

  10. The linking project • Web service for display - Output = JSONP • display in ALEPH OPAC http://lida.bnl.lu/authors.php? sys=000406978 &author=Asselborn, Jean-Claude &callback=showCnl • display in Autorenlexikon http://lida.bnl.lu/authors.php? id=263 &did=149 &callback=showBnl

  11. The linking project • Display matches in the ALEPH OPAC • Language specific

  12. The linking project • Display matches in the ALEPH OPAC • Pseudonyms / alternative names

  13. The linking project • Display matches in the ALEPH OPAC • Multiple matches for a single bibliographic record

  14. The linking project • Validation service

  15. The linking project • Phase 2 & future steps: • Display in Primo • Links between the authority database and Autorenlexikon • VIAF • Matching based on ID’s (?) • Integrate other systems (Digitool)

  16. The linking project Questions, remarks, suggestions? Roxana Popistaşu Roxana-Maria.Popistasu@bnl.etat.lu

More Related