TCDL 2009 keynote: Better living through linking

  • 22,404 views
Uploaded on

Slides from the talk I gave at the TCDL 2009 conference on May 27, 2009. Full writeup at http://onebiglibrary.net/story/tcdl-2009-talk-better-living-through-linking.

Slides from the talk I gave at the TCDL 2009 conference on May 27, 2009. Full writeup at http://onebiglibrary.net/story/tcdl-2009-talk-better-living-through-linking.

More in: Technology , Design
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
22,404
On Slideshare
0
From Embeds
0
Number of Embeds
4

Actions

Shares
Downloads
75
Comments
1
Likes
14

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Better Living through Linking Daniel Chudnov - 2009-05-27 - dchud at umich edu Texas Conference on Digital Libraries 2009
  • 2. MY OPINIONS DO NOT REFLECT THOSE OF: MY EMPLOYER THE US GOV’T PRES. BARACK OBAMA THE DETROIT RED WINGS
  • 3. • doing “web” better • linking data • steps you can take today
  • 4. 1. doing “web” better
  • 5. we’ve been building a web for a long time
  • 6. Photo cc-sa by osunick on flickr, http://tinyurl.com/oy8qw942
  • 7. which brings us to about, say, 1996.
  • 8. xml 1997
  • 9. db-backed sites 1998
  • 10. xml-backed sites 1999
  • 11. blog tools 2001
  • 12. better search 2002
  • 13. rss openurl oai-pmh srw/u opensearch microformats
  • 14. redesign redesign redesign redesign redesign redesign
  • 15. scripts includes templates frameworks cms seo
  • 16. User. Generated. Content. OMG ROFLMAO LOLZ
  • 17. how we use the web evolves
  • 18. how we build the web evolves
  • 19. it’s not done yet, but
  • 20. we are still building a web
  • 21. here’s what’s next
  • 22. 2. linking data
  • 23. links matter
  • 24. just ask Google
  • 25. but we knew that
  • 26. for example
  • 27. which, basically, was this
  • 28. the web is made of links
  • 29. but wait there’s more
  • 30. which, basically, was this
  • 31. but nobody knows that
  • 32. ...unless they know to look...
  • 33. ...which is the problem.
  • 34. more to the point
  • 35. Google won’t find this.
  • 36. http://authorities.loc.gov/cgi-bin/Pwebrecon.cgi? AuthRecID=2852966&v1=1&HC=3&SEQ=2009052703254 5&PID=XGImKyGgg1Cofw8uO3IFxAvS
  • 37. what’s wrong with this picture?
  • 38. system info http://authorities.loc.gov/cgi-bin/Pwebrecon.cgi? AuthRecID=2852966&v1=1&HC=3&SEQ=2009052703254 5&PID=XGImKyGgg1Cofw8uO3IFxAvS unknowable session info info
  • 39. unbookmarkable
  • 40. screenscraping required
  • 41. unscriptable
  • 42. item record authority record
  • 43. not linked
  • 44. a holdings record doesn’t help Google
  • 45. but wait, there’s more
  • 46. not connected
  • 47. not findable
  • 48. not relevant
  • 49. ouch.
  • 50. despite our efforts
  • 51. the expense of digitizing
  • 52. care and feeding of cranky coders
  • 53. the overhead of authority control
  • 54. we count on Google to guess at relevance
  • 55. inside our systems we tweak and improve
  • 56. across our systems we can only hope
  • 57. time to do better
  • 58. enter Linked Data
  • 59. “Linked Data” is data in the web
  • 60. “Linked Data” is a movement
  • 61. “Linked Data” is dogma
  • 62. “Linked Data” is worth a close look
  • 63. so what is it?
  • 64. a way to link better
  • 65. a way to make concepts explicit
  • 66. a way to connect our stuff
  • 67. a way to connect these together item record authority record
  • 68. draw our stuff deeper into the web
  • 69. not just files to download but part of the web
  • 70. how?
  • 71. use URIs as names for things use HTTP URIs provide useful information include links to other URIs http://www.w3.org/DesignIssues/LinkedData.html
  • 72. break down concepts make them “pages”
  • 73. the new the old
  • 74. bad URL screenscraping required few links out no links in the old
  • 75. the new good URL alternate formats some links out more links in
  • 76. LCCN Permalink alternate formats more links out clean URI http://lccn.loc.gov/84759993
  • 77. discoverable, parseable alternate formats
  • 78. apply these rules everywhere
  • 79. rel=alternate resource URI rel=contents (already has) resource URI resource URI resource URI rel=alternate
  • 80. arrows become cross-references
  • 81. why?
  • 82. it becomes crawl-able mine-able
  • 83. integrated access through smart crawl / index
  • 84. precision improves with rich metadata explicitly linked
  • 85. recall improves with explicit links through authority recs
  • 86. bring precision / recall of clunky OPACs to open web
  • 87. this is doing web stuff better
  • 88. just by doing HTML / HTTP
  • 89. use URIs as names for things use HTTP URIs provide useful information include links to other URIs http://www.w3.org/DesignIssues/LinkedData.html
  • 90. doesn’t fit the web, it is the web
  • 91. many examples already
  • 92. LIBRIS id.loc.gov chronicling america
  • 93. if i squint just right...
  • 94. the “LOD cloud” a “ready reference” collection
  • 95. make this useful turn this into linked data
  • 96. seems obvious, right?
  • 97. 3. steps you can take today
  • 98. how to link your data
  • 99. (or, About All That Other Stuff You Have)
  • 100. use URIs as names for things use HTTP URIs provide useful information include links to other URIs http://www.w3.org/DesignIssues/LinkedData.html
  • 101. first: clean, cool URIs for data concepts
  • 102. instead of this: /search?subject=Strayhorn,+Billy
  • 103. do this: /subject/lccn/n81072976
  • 104. easy to implement today
  • 105. easy to redirect tomorrow
  • 106. next: offer data views
  • 107. use <a rel=___ href=___> <link rel=___>
  • 108. offer up MARC, or JSON, or RDF, or ...
  • 109. next: relate your data to established authorities
  • 110. your search results backed by shared authority records
  • 111. put it all together
  • 112. visit /subject/lccn/n81072976 • get your content results • get alternate data views (concept record) • get links to other useful data • get links to authorized form
  • 113. all that’s easy
  • 114. i promise
  • 115. the next part’s hard
  • 116. how to make it last
  • 117. if your site breaks when links break cache and link yourself
  • 118. instead of just this
  • 119. do this UChicago same as cache
  • 120. just like we do in ILS/OPACs
  • 121. but, yknow, the web way
  • 122. so if a remote link breaks your local links still work
  • 123. also, proxy concepts
  • 124. your /subject/lccn/n81072976 == my /subject/lccn/n81072976
  • 125. but in your app
  • 126. make every cache its own linked data source
  • 127. instead of just this UChicago same as cache
  • 128. enable this UChicago same as cache same as same as same as same as
  • 129. if one goes down the others live on
  • 130. if others live on it’s all still linked
  • 131. if it’s all still linked we can keep adding
  • 132. linked data that lasts
  • 133. i think
  • 134. summary • making the web better • follow Linked Data practices • easy changes to make now
  • 135. summary • get more value from our data • get more users to our data • make relevance explicit
  • 136. thanks! dchud at umich edu onebiglibrary.net twitter.com/dchud