Your SlideShare is downloading. ×
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Adrian Stevenson (UKOLN) – Linked Open Copac Archives Hub (LOCAH) project – use of Timemap for visualising linked data

994

Published on

Pecha Kucha presented at Repository Fringe 2011.

Pecha Kucha presented at Repository Fringe 2011.

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
994
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
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
  • Copac a union catalogue Both successful JISC services running for many years now Locah is a research project – will have to see if go into service with LD interface
  • http://www.w3.org/DesignIssues/LinkedData.html
  • In hypertext web sites it is considered generally rather bad etiquette not to link to related external material. The value of your own information is very much a function of what it links to, as well as the inherent value of the information within the web page.  So it is also in the Semantic Web. Remember, this is about machines linking – machines need identifiers; humans generally know when something is a place or when it is a person. BBC + DBPedia + GeoNames + Archives Hub + Copac + VIAF = the Web as an exploratory space
  • This also an example of aggregating data
  • More aggregation
  • Data can be integrated from many diff sources
  • Ex
  • “ lower level” units interpreted in context of the higher levels of description Arguably “incomplete” without the contextual data. Relations are asserted, e.g. member-of/component-of But there is no requirement or expectation that data consumers will follow the links describing the relations
  • Transcript

    • 1. LOCAH Project
      • L inked O pen C opac and A rchives H ub
      • Funded by #JiscEXPO 2/10 ‘Expose’ call
        • 1 year project. Started August 2010
      • Partners & Consultants:
        • UKOLN – Adrian Stevenson, Julian Cheal
        • Mimas – Jane Stevenson, Bethan Ruddock, Yogesh Patel
        • Eduserv – Pete Johnston
        • Talis – Leigh Dodds, Tim Hodson
        • OCLC - Ralph LeVan, Thom Hickey
        • Ed Summers
      • http://blogs.ukoln.ac.uk/locah/
    • 2. Archives Hub and Copac
      • UK National Data Services based at Mimas
      • Archives Hub is an aggregation of archival descriptions from archive repositories across the UK
        • http://archiveshub.ac.uk
      • Copac provides access to the merged library catalogues of libraries throughout the UK, including all national libraries
        • http://copac.ac.uk
    • 3. What is LOCAH Doing?
      • Part 1: Exposing Archives Hub & Copac data as Linked Data
      • Part 2: Creating a prototype visualisation
      • Part 3: Reporting on opportunities and barriers
    • 4. Linked Data Design Issues
      • URIs
      • LD Design Issues
      • Triples
      http://www.w3.org/DesignIssues/LinkedData.html
    • 5. Triples
      • Triples statements
        • ‘ Things’ have ‘properties’ with ‘values’
        • Subject – Predicate - Object
      • Triples are the basis of RDF
      Archival Resource Repository Provides Access To The Rolling Stones Keith Richards Is Member Of
    • 6. We’re Linking Data!
      • If something is identified, it can be linked to
      • We take items from one dataset and link them to items from other datasets
      BBC VIAF DBPedia Archives Hub Copac GeoNames
    • 7. Enhancing our data
      • Already have some links:
        • Time - reference.data.gov.uk URIs
        • Location - UK Postcodes URIs and Ordnance Survey URIs
        • Names - Virtual International Authority File
          • Matches and links widely-used authority files - http://viaf.org/
        • Names - DBPedia
      • Also looking at:
        • Subjects - Library Congress Subject Headings and DBPedia
    • 8. http://data.archiveshub.ac.uk/
    • 9. http://data.archiveshub.ac.uk/id/person/nra/webbmarthabeatrice1858-1943socialreformer
    • 10.  
    • 11. How are we creating the Visualisation Prototype?
      • Based on researcher use cases
      • Data queried from Sparql endpoint
      • Use tools such as Simile, Many Eyes, Google Charts
    • 12. Visualisation Prototype
      • Using Timemap –
        • Googlemaps and Simile
        • http://code.google.com/p/timemap /
      • Early stages with this
      • Will give location and ‘extent’ of archive.
      • Will link through to Archives Hub
    • 13. Linking Lives Project
      • Starts September 2011
      • Builds on Locah work
    • 14. The Key Benefit of Linked Data (?)
      • Mashups work against a fixed set of data sources
        • Hand crafted by humans
        • Don’t integrate well
      • Linked Data promises an unbound global data space
        • Easy dataset integration
        • Generic ‘mesh-up’ tools
    • 15. Matching Subjects
    • 16. Matching Places
    • 17. Sustainability
      • Can you rely on data sources long-term?
      • Ed Summers at the Library of Congress created http://lcsh.info
      • Linked Data interface for LOC subject headings
      • People started using it
    • 18. Scalability / Provenance Example by Bradley Allen, Elsevier at LOD LAM Summit, SF, USA
      • Same issue with attribution
      • Solutions: Named graphs? Quads?
      • Best Practice
    • 19. Data Modelling
      • Complexity
        • Archival description is hierarchical and multi-level
      • Dirty Data
      Licensing
      • ‘ Ownership’ of data
      • Hard to track attribution
      • CC0 for Archives Hub and Copac data
    • 20. Linked Data for Repositories?
      • Repository data can ‘work harder’
      • New channels into your data
      • New connections with other data sources
      • Researchers are more likely to discover sources
      • ‘ Hidden' collections of repositories become of the Web

    ×