Aggregation Using Linked Data – LOCAH Project Experiences
Download as PPT, PDF1 like4,103 views
The LOCAH project, managed by Adrian Stevenson, focuses on linking data from the UK Archives Hub and Copac, providing aggregation of archival descriptions and library catalogues. It aims to expose this data as linked data, create visualizations, and report on integration challenges, while also addressing questions regarding data linking, sustainability, and long-term reliability. Through the use of linked data, the project seeks to enhance data discoverability and enable researchers to access a wider array of archival resources.
Aggregation Using Linked Data – LOCAH Project Experiences
- 1. UKOLN is supported by: Aggregation Using Linked Data – LOCAH Project Experiences 23rd June 2011 OAI7, Geneva, Switzerland Adrian Stevenson LOCAH Project Manager
- 2. 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/ tag: #locah
- 3. 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
- 4. 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
- 5. We’re Aggregating 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
- 6. 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. ‘ Aggregates’ property points to http://www.openarchives.org/ore/terms/aggregates
- 10. 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
- 12. BBC Music
- 13. APIs, Mashups and 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
- 14. Aggregation / Integration Challenges
- 18. 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
- 19. Library of Congress Subject Headings
- 20. Scalability Will the Web of Data scale? Example by Bradley Allen, Elsevier at LOD LAM Summit, SF, USA
- 21. 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
- 22. Linked Data the Way for Aggregation? Enables ‘straightforward’ aggregation of wide variety of data sources New channels into your data services Researchers are more likely to discover sources ‘ Hidden' collections of repositories become of the Web
- 23. Questions for Discussion Will using vocabularies and ontologies always be too difficult? Or will the tools appear? – MS Access for Linked Data? Will the Web of Data scale?
- 24. What constitutes data worth linking to? How to find datasets suitable for interlinking? How to make my dataset worth linking to? How to encourage others to link to my data? What is the added value of links? How to determine the quality of a link? Questions if you’ve bought in
- 25. Attribution and CC License Sections of this presentation adapted from materials created by other members of the LOCAH Project This presentation available under creative commons Non Commercial-Share Alike: http://creativecommons.org/licenses/by-nc/2.0/uk/
Editor's Notes
- #4: 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
- #6: 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
- #11: This also an example of aggregating data
- #12: More aggregation
- #14: Data can be integrated from many diff sources
- #21: Ex
- #22: “ 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