Your SlideShare is downloading. ×
0
Monitoring and evaluating APIs - Uganda
Monitoring and evaluating APIs - Uganda
Monitoring and evaluating APIs - Uganda
Monitoring and evaluating APIs - Uganda
Monitoring and evaluating APIs - Uganda
Monitoring and evaluating APIs - Uganda
Monitoring and evaluating APIs - Uganda
Monitoring and evaluating APIs - Uganda
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

Monitoring and evaluating APIs - Uganda

251

Published on

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

  • Be the first to like this

No Downloads
Views
Total Views
251
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
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

Transcript

  • 1. What difference did it make? Date: 06:01:2011
  • 2. Evaluating an Open API <ul><li>Who should benefit from an Open API? </li></ul><ul><li>How will they benefit? i.e. what will be different if the Open API is successful? </li></ul><ul><li>How will you know if those benefits are realised? </li></ul>
  • 3. How are we evaluating MK4D? <ul><li>Monitoring outputs – what did we do? </li></ul><ul><ul><li>webstats, finance, publications, reach figures </li></ul></ul><ul><ul><li>Event reports </li></ul></ul><ul><li>Evaluating outcomes – what difference did it make? </li></ul><ul><ul><li>Principles of outcome mapping </li></ul></ul><ul><ul><li>Interviews, Surveys, ‘tests’, data analysis </li></ul></ul><ul><li>Improvement - what lessons did we learn? </li></ul><ul><ul><li>Event reports </li></ul></ul><ul><ul><li>Learning labs </li></ul></ul>
  • 4. Evaluating an Open API <ul><li>Who should benefit from an Open API? </li></ul><ul><li>Participating institutes </li></ul><ul><li>Users </li></ul><ul><li>Producers </li></ul>
  • 5. Evaluating an Open API <ul><li>How will they benefit? </li></ul><ul><li>Participating institutes </li></ul><ul><li>- Share info among partners </li></ul><ul><li>- more efficacy </li></ul><ul><li>- more hits </li></ul><ul><li>- less human error e.g. automation doesn't rely on one person </li></ul><ul><li>- increases trust of data received </li></ul><ul><li>- increased creativity </li></ul>
  • 6. Evaluating an Open API <ul><li>How will they benefit? </li></ul><ul><li>Users </li></ul><ul><li>- less work searching for info </li></ul><ul><li>- start using online content </li></ul><ul><li>- increased use of content </li></ul><ul><li>- access more dynamic data therefore more diverse perspectives </li></ul><ul><li>- holistic view </li></ul><ul><li>- balanced decisions </li></ul><ul><li>- increase quality of research output </li></ul>
  • 7. Evaluating an Open API <ul><li>How will they benefit? </li></ul><ul><li>Producers </li></ul><ul><li>- avoid duplication </li></ul><ul><li>- reach wider audience </li></ul><ul><li>- unleash creativity </li></ul><ul><li>- outreach/publicity/exposure </li></ul>
  • 8. Evaluating an Open API <ul><li>How will you know if those benefits are realised? </li></ul>

×