The Other Side of the Journal ToCs Interface

1,818 views
1,735 views

Published on

Presentation given to Journal ToCs workshop on 20 Nov 2009, examining where the Journal ToCs API fits into the repository ecology: what is its role and how might it interact with institutional repository systems.

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

No Downloads
Views
Total views
1,818
On SlideShare
0
From Embeds
0
Number of Embeds
438
Actions
Shares
0
Downloads
7
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

The Other Side of the Journal ToCs Interface

  1. 1. The Other Side of the Interface . or The sound of one hand clapping Phil Barker, philb@icbl.hw.ac.uk
  2. 2. Journal ToCs Place in the Repository Ecosystem <ul><li>Ecology is the study of systems that are complex, dynamic, and full of interacting entities and processes. </li></ul><ul><li>… ecology, and examples of the ecosystems it studies, may offer a useful analogy to inform the task of understanding and articulating the interactions between users, repositories, and services and the information environments in which they take place. </li></ul><ul><li>http://ie-repository.jisc.ac.uk/272/ </li></ul>
  3. 3. An ecosystem <ul><li>Species </li></ul><ul><li>Resources </li></ul><ul><li>Interactions </li></ul>Image from D. Kumar (1992) Fish culture in undrainable ponds: A manual for extension, FAO Fisheries Technical Paper No. 325. Rome, FAO http://www.fao.org/docrep/003/T0555E/T0555E00.HTM . Image © Food and Agricultural Organisation of the United Nations
  4. 4. A Repository Ecosystem? <ul><li>Species: </li></ul><ul><ul><li>Repositories </li></ul></ul><ul><ul><li>Library services </li></ul></ul><ul><ul><li>Web services </li></ul></ul><ul><ul><li>Repository managers </li></ul></ul><ul><ul><li>Researchers </li></ul></ul><ul><ul><li>Journal publishers </li></ul></ul>
  5. 5. A Repository Ecosystem? <ul><li>Resources </li></ul><ul><ul><li>Information resources </li></ul></ul><ul><ul><ul><li>Journal papers, data, metadata </li></ul></ul></ul><ul><ul><li>Money </li></ul></ul><ul><ul><li>Time / attention </li></ul></ul>
  6. 6. A Repository Ecosystem? <ul><li>Interactions </li></ul><ul><ul><li>Human-Human </li></ul></ul><ul><ul><li>Human-Machine </li></ul></ul><ul><ul><li>Machine-Machine: </li></ul></ul><ul><ul><ul><li>APIs, RSS Feeds, HTTP </li></ul></ul></ul>
  7. 7. Repository Ecology <ul><li>We can study many aspects of the repository ecosystem </li></ul><ul><li>One example is “Metadata in an ecosystem of presentation dissemination” Robertson, Barker & Mahey, Proc. Int’l Conf. on Dublin Core and Metadata Applications 2008 http://blogs.cetis.ac.uk/johnr/2008/09/25/metadata-in-an-ecosystem-of-presentation-dissemination/ http:// dcpapers. dublincore .org/ojs/pubs/article/viewFile/938/934 </li></ul>
  8. 9. JournalToCs API
  9. 10. What is an API <ul><li>An application programming interface (API) is an interface to a software program that allows other software to interact with it. </li></ul><ul><li>An API is an abstraction, a set of specifications; to implement one you need code in the server and the client. </li></ul>
  10. 11. JournalToCs API <ul><li>One side of an interface, what's the other? </li></ul>
  11. 12. Possible complements <ul><li>An RSS feed reader used by the repository manager </li></ul><ul><ul><li>Pretty much what we have now </li></ul></ul><ul><ul><li>No integration with workflow </li></ul></ul>
  12. 13. Possible Complements 3 <ul><li>Response to query from the repository. </li></ul><ul><li>Would need work on the client side </li></ul><ul><li>Need to ask for data specifcally </li></ul><ul><li>Pull data into where it is used </li></ul>
  13. 14. Possible complements (3) <ul><li>Embed RSS alerts into repository </li></ul><ul><ul><li>Would need work on client side </li></ul></ul><ul><ul><li>Need to set up alert request (then let it run) </li></ul></ul><ul><ul><li>Pull data to where it is used </li></ul></ul>
  14. 15. Possible complements (3) <ul><li>Push alerts to the repository (XMPP, cf Jabber, Google Wave) </li></ul><ul><ul><li>Would require work on server and client. </li></ul></ul><ul><ul><li>We push data to you when it is there rather than your system asking if there is anything. </li></ul></ul><ul><ul><li>Puts the data where it is used. </li></ul></ul>
  15. 16. Possible complements <ul><li>All except the most basic option require </li></ul><ul><ul><li>Further work => Further funding </li></ul></ul><ul><ul><li>Clarification of your requirements </li></ul></ul><ul><ul><li>Liaison with developers of target system (IR, VRE) </li></ul></ul>
  16. 17. Summary <ul><li>The JournalToCs API serves and important role in the repository ecology, but implementing at JournalToCs is only half the story. </li></ul>

×