1 / 8

Achieving Interoperability: Challenges and Opportunities for Stakeholders

Explore the benefits and threats of interoperable content and repository APIs, and discover how to leverage them effectively. Address the concerns of cataloguers, OA advocates, web/IS managers, developers, repository managers, and researchers.

bvirgil
Download Presentation

Achieving Interoperability: Challenges and Opportunities for Stakeholders

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Interoperability Stakeholders Peter Cliff, Research Officer, UKOLN, University of Bath, UK SUETr Interoperability Workshop, The LSE Library, December 2008 UKOLN is supported by: This work is licensed under a Creative Commons LicenseAttribution-ShareAlike 2.0

  2. Political/Human Interoperability • Interoperability is more than just technical interoperability: • Institutions fear loss of control • Staff lack skills to support complex systems and a dispersed user community • Process change and staff & user training is required

  3. Stakeholders • Cataloguer & Open Access fan • Web/IS Manager/Developer • Repository Manager • Researcher

  4. The Task While trying to imagine yourself in the role consider: • What are the benefits and/or threats of "interoperable content"/repository APIs to the repository? (Either incoming or outgoing material). • In order to work with these APIs what do I need to put into/do with the repository? • Is there anything I want the repository to work with that it doesn't already? • How might I make that happen? What could I use? Where do I look?

  5. Cataloguer & OA Advocate • Threat to the repository role as source of Open Access material. • APIs provide access to systems that cannot be trusted. • APIs might generate poor quality metadata. • Opportunity to create bespoke cataloguer tools very welcome!

  6. Web/IS Manager/Developer • Giving control to third party sites • Inappropriate content/"back door“ • Speed • Reliability • Web Standards? • Consistency • "Linked Data"

  7. Repository Manager • Increased Usage/Exposure • Easier advocacy • Bespoke tools for: • depositor/submitter • curators • Alerting services • Complexity – interoperability seems too hard! • Where will the works end up?

  8. Researcher • Desires a holistic, integrated document/research management system • Alerting services • Improved visibility of research • Community tools • Bespoke/integrated repository submission

More Related