Successfully reported this slideshow.

More Related Content

Related Books

Free with a 14 day trial from Scribd

See all

Presentation elag 2013

  1. 1. Triple bypass Martin Malmsten, Markus Sköld, Niklas Lindström, Anna Berggren Tuesday, June 4, 13 Hi, and thank you for having us. My name is Martin Malmsten and I am head of Software Development at the Libris department, at the National Library of Sweden and I will be joined by some of my collegues later on in the presentation. Libris is the Swedish Union Catalogue in which university, and some public, libraries traditionally catalogue their printed material. It is a centrally maintained catalogue which means that we do have national identifiers and we do not spend all of our time doing deduplication. We are here to talk about the new catalogue and cataloguing client being built by Libris and some of the motivations behind building it.
  2. 2. Libris LOD est. 2008 Tuesday, June 4, 13 We’ve had a Linked Open Data implementation for quite some time covering the whole of Libris including the authority file with persons, organizations, etc. This is very nice and all and you could say that the Libris implementation is like a flower ... but there is just one problem.
  3. 3. Libris LOD est. 2008 ... striiiings ... Tuesday, June 4, 13 the Linked Data essentially grows on the back of this Zombie named MARC. Marc has been declared dead quite a few times, at least the last five ELAGS I assume.
  4. 4. Libris LOD est. 2008 Tuesday, June 4, 13 Actually though, he is doing quite well, for being undead at least. A huge part of our infrastructure, and I mean yours too, not just ours, is still MARC based. A lot of workflows are MARC-based. We still ship them around.
  5. 5. Why change? •Flexibility •Get rid of old workflows •Digitization projects •Control •Format agnostisism •SwePub •National Discovery? •Storing objects Tuesday, June 4, 13 Libris faces a number of challenges. But also to be a better web citizen ...
  6. 6. my datasomeones data Tuesday, June 4, 13 Because publishing Linked Data is not enough. A lot of the potential for efficiency and quality lies in consuming Linked Data. This has a profound change in how we do systems design. If there is Ofcourse the real challenge here is NOT really to create a linked data catalogue. The challenge is to maintain the existing funxtionality (a lot of which is centered around MARC) and transition it to something new. Also transition into something that will be easier to transition OUT of. Because a lot of what we need is already provided “by the web”.
  7. 7. my datasomeones data feed Tuesday, June 4, 13 Because publishing Linked Data is not enough. A lot of the potential for efficiency and quality lies in consuming Linked Data. This has a profound change in how we do systems design. If there is Ofcourse the real challenge here is NOT really to create a linked data catalogue. The challenge is to maintain the existing funxtionality (a lot of which is centered around MARC) and transition it to something new. Also transition into something that will be easier to transition OUT of. Because a lot of what we need is already provided “by the web”.
  8. 8. The web is distributed Tuesday, June 4, 13 The web is distributed, and it is meant to be distributed. One could say that that is the main thing. Which is also why ...
  9. 9. An aggregate is not a web ... neither is a cloud Tuesday, June 4, 13 ... an aggregate is not a web. And a cloud is not a web either.
  10. 10. Keep MARC on the outside Tuesday, June 4, 13 So we do need to coexist with MARC, probably for some time to come. But we can keep MARC on the outside of the system, not let it be an intergral part that influences core design. In genreal it’s a good idea to keep the undead on the outside and I kinda wished I had drawn a picture of that
  11. 11. Triple bypass Martin Malmsten, Markus Sköld, Niklas Lindström, Anna Berggren Tuesday, June 4, 13
  12. 12. Tuesday, June 4, 13
  13. 13. http://github.com/libris/librisxl/ Tuesday, June 4, 13
  14. 14. Triple bypass Martin Malmsten, Markus Sköld, Niklas Lindström, Anna Berggren Tuesday, June 4, 13
  15. 15. When you’re up to your neck in alligators, it’s hard to remember that the original aim was to drain the swamp CC-BY: Basking Gator (Matthew Paulson) Tuesday, June 4, 13
  16. 16. The Swamp ... ... The Gators ... ... The Mission Tuesday, June 4, 13
  17. 17. 000: 00887cam a2200277 a 4500 008 960214s1996 sw 000 0aswe # 100 1 _ $aJansson, Tove,$d1914-2001# 245 0 0 $aAnteckningar från en ö /$cTove Jansson, Tuulikki Pietilä 260 _ _ $aStockholm :$bBonnier,$c1996 ;$e(Finland)# Tuesday, June 4, 13
  18. 18. The Instruments JSON-LD ElasticSearch AngularJS Tuesday, June 4, 13
  19. 19. The Map { "260": { "domainEntity": "Instance", "splitLink": [ {"codes": ["a", "b", "c"], "addLink": "publication"}, {"codes": ["e", "f", "g"], "addLink": "manufacture"} ], "rangeEntity": "ProviderEvent", "$a": {"link": "place", "rangeEntity": "Place", "property": "label"}, "$b": {"property": "providerName"}, "$c": {"property": "providerDate"}, "$e": {"link": "place", "rangeEntity": "Place", "property": "label"}, "$f": {"property": "providerName"}, "$g": {"property": "providerDate"}, "$3": {"property": "scopeNote"} }, ... Tuesday, June 4, 13
  20. 20. The Flower { "@type": ["Instance", "Book"], "@id": "bib/7149593", "title": "Anteckningar från en ö", "publication": [ { "@type": "ProviderEvent", "providerName": "Bonnier,", "providerDate": "1996", "place": {"@type": "Place", "label": "Stockholm"} } ], "manufacture": [ { "@type": "ProviderEvent", "place": {"@type": "Place", "label": "Finland"} } ], ... Tuesday, June 4, 13
  21. 21. The Soil { "@context": { "xsd": "http://www.w3.org/2001/XMLSchema#", "foaf": "http://xmlns.com/foaf/0.1/", "bibo": "http://purl.org/ontology/bibo/", "@vocab": "http://bibframe.org/vocab/", "Record": "foaf:Document", "authorList": {"@id": "bibo:authorList", "@container": "@list"}, "pubYear": {"@id": "pubDate", "@type": "xsd:gYear"}, ... Tuesday, June 4, 13
  22. 22. The Path <bib/7149593> :instanceOf <work/anteckningar-fran-en-o> . <work/anteckningar-fran-en-o> :creator <person/tove-jansson>, <person/tuulikki-pietilä> . Tuesday, June 4, 13
  23. 23. The Turtle <bib/7149593> a :Instance, bibo:Book; :instanceOf <work/anteckningar-fran-en-o>; :title "Anteckningar från en ö"; :publication [ a :ProviderEntity; :place [ a :Place; rdfs:label "Stockholm" ]; :providerDate "1996"; :providerName "Bonnier," ]; :manufacture [ a :ProviderEntity; :place [ a :Place; rdfs:label "Finland" ] ] . Tuesday, June 4, 13
  24. 24. CC-BY CC-BY: Basking Gator (Matthew Paulson) Tuesday, June 4, 13
  25. 25. Triple bypass Martin Malmsten, Markus Sköld, Niklas Lindström, Anna Berggren Tuesday, June 4, 13
  26. 26. Tuesday, June 4, 13
  27. 27. Tuesday, June 4, 13
  28. 28. Tuesday, June 4, 13
  29. 29. Tuesday, June 4, 13

Editor's Notes

  • Hi, and thank you for having us. My name is Martin Malmsten and I am head of Software Development at the Libris department, at the National Library of Sweden and I will be joined by some of my collegues later on in the presentation. Libris is the Swedish Union Catalogue in which university, and some public, libraries traditionally catalogue their printed material. It is a centrally maintained catalogue which means that we do have national identifiers and we do not spend all of our time doing deduplication. We are here to talk about the new catalogue and cataloguing client being built by Libris and some of the motivations behind building it.
  • We’ve had a Linked Open Data implementation for quite some time covering the whole of Libris including the authority file with persons, organizations, etc. This is very nice and all and you could say that the Libris implementation is like a flower ... but there is just one problem.
  • the Linked Data essentially grows on the back of this Zombie named MARC. Marc has been declared dead quite a few times, at least the last five ELAGS I assume.
  • Actually though, he is doing quite well, for being undead at least. A huge part of our infrastructure, and I mean yours too, not just ours, is still MARC based. A lot of workflows are MARC-based. We still ship them around.
  • Libris faces a number of challenges. But also to be a better web citizen ...
  • Because publishing Linked Data is not enough. A lot of the potential for efficiency and quality lies in consuming Linked Data. This has a profound change in how we do systems design. If there is Ofcourse the real challenge here is NOT really to create a linked data catalogue. The challenge is to maintain the existing funxtionality (a lot of which is centered around MARC) and transition it to something new. Also transition into something that will be easier to transition OUT of. Because a lot of what we need is already provided “by the web”.
  • Because publishing Linked Data is not enough. A lot of the potential for efficiency and quality lies in consuming Linked Data. This has a profound change in how we do systems design. If there is Ofcourse the real challenge here is NOT really to create a linked data catalogue. The challenge is to maintain the existing funxtionality (a lot of which is centered around MARC) and transition it to something new. Also transition into something that will be easier to transition OUT of. Because a lot of what we need is already provided “by the web”.
  • The web is distributed, and it is meant to be distributed. One could say that that is the main thing. Which is also why ...
  • ... an aggregate is not a web. And a cloud is not a web either.
  • So we do need to coexist with MARC, probably for some time to come. But we can keep MARC on the outside of the system, not let it be an intergral part that influences core design. In genreal it’s a good idea to keep the undead on the outside and I kinda wished I had drawn a picture of that
  • ×