Opening up: bibliographic data sharing & interoperability

1,893 views
1,827 views

Published on

Presentation given at CILIP multimedia and information technology group conference, April 2013

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,893
On SlideShare
0
From Embeds
0
Number of Embeds
1,182
Actions
Shares
0
Downloads
1
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Opening up: bibliographic data sharing & interoperability

  1. 1. Bethan Ruddock @bethanarMmIT CloudBusting, April 2013
  2. 2. You have valuable data that you want to share… … but it’s locked inside your systems Image used under CC licence from http://www.flickr.com/photos/kdashy/2678539087/
  3. 3. Push discovery, help researchers find more stuff,promote use of your collections, enable coolthings like data mining and visualisations,combine with other data sets, make the most ofyour time and effort, store data in sustainableformats, allow others to enhance yourdata, embed in other sites and catalogues,enable global access, back-up valuabledata, benchmark & collaborate
  4. 4. Image used under a CC licence fromhttp://www.flickr.com/photos/brenda-starr/4498078166/
  5. 5. Store & protect Combine multiple data sets Images used under CC licence from http://www.flickr.com/photos/austin2179/2327574713/ and http://www.flickr.com/photos/streamishmc/3069595776
  6. 6. Store & protect Some cloud services are designed just for storage Or for storage and client- side collaboration Images used under CC licence from http://www.flickr.com/photos/austin2179/2327574713/ and http://www.flickr.com/photos/lollyman/4424552903
  7. 7. For others, storage won’tbe the main function They’ll be designed to ‘do stuff’ with the data: combine it with other datasets; make it available in new formats & interfaces Store & combine multiple datasets Images used under CC licence from http://www.flickr.com/photos/austin2179/2327574713/ and http://www.flickr.com/photos/streamishmc/3069595776
  8. 8. These services will usually be defined by what they dowith the data. You might not even think of them as cloud services…
  9. 9. The format your data needs to be in will dependwhich cloud service you’re sending it to, and whatyou want done with that data.Storage & collaboration services: Native data format, or whatever you & your collaborators need to work in Try to choose compact & sustainable formatsCombination services: Whatever format the service requires This will usually be the same as the other data sets, or transformable/interoperable
  10. 10. Check what formats you can export data in. CSV? SQL text format? HTML? Plain text?Consider: What format is most appropriate?Archive catalogues – EAD?Library catalogues – MARC? MODS XML?Linked data – RDF? Dublin Core XML? Is it interoperable? Consistent? Transformable? Will it enable the service to meet its aims? How is it licensed?
  11. 11. Image used under CC licence fromhttp://www.flickr.com/photos/tonynewell/1463945828/
  12. 12. Are there barriers to sharing your data? Licensing & data ownership Loss of control Legal barriers to sharing No time/resource to output dataWhat are the risks of sharing? Lose access to service Data compromisedWhat are the risks of not sharing? Data is isolated in a ‘silo’ Don’t meet sharing/outreach objectives Only have single, local copy of data
  13. 13. When choosing a cloud service:Why do you want to open yourdata to the cloud? Does this service meet your needs? Does it meet your users needs?Is your data in the right format? Or can you transform it to be?Can you get your data out of thecloud service? In an appropriate format?Is the service interoperable? Does the service put a certainIs the service sustainable? licence on your data? Who do they share it with? Image used under a CC licence from http://www.flickr.com/photos/kky/704056791/
  14. 14. Image used under CC licence fromhttp://www.flickr.com/photos/justanotherhuman/5795955558/
  15. 15. Pairs of resource descriptions, describing the sameresource using different schemas.Does one of these schemas describe the resource betterthan another?What aspects of the resource have they described well?Have they missed aspects, or described them badly?How interoperable is each description? For humans? Forcomputers?What would you need to do to this data to share it withothers?What purpose do you think each schema would best beused for?
  16. 16. bethan.ruddock@manchester.ac.uk @bethanar Image used under CC licence from http://www.flickr.com/photos/theilluminated/5386099858/

×