Introducing Dspace @ ILRI Peter Ballantyne 1 December 2010
CGIAR RESEARCH OUTPUTS ARE THEY TRULY ACCESSIBLE?
Not really … <ul><li>They are not captured </li></ul><ul><li>They are locked up behind passwords </li></ul><ul><li>They ar...
Who cares? Why be accessible? <ul><li>Our data information or knowledge assets should have benefits that can travel across...
AAA <ul><li>Availability  - able to identify a ‘publication’ (metadata at least) </li></ul><ul><li>Accessibility – able to...
AAA Pathways <ul><li>Promising technical and institutional routes to more or better accessibility </li></ul><ul><ul><li>Cr...
<ul><li>Repository of outputs of people and projects (hosted at ILRI) </li></ul><ul><li>Publishing and alerting platform <...
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Choices we made <ul><li>Organize contributions by content type (publications, multi-media, articles datasets, etc) </li></...
Workflows <ul><li>Dspace ‘the’ ILRI way to publish on the ILRI web … </li></ul><ul><li>Projects need ‘archives’ and visibi...
 
Future ? <ul><li>Index/make available limited access items (to the CGIAR with Active Directory?) </li></ul><ul><ul><li>Ful...
 
 
 
 
Upcoming SlideShare
Loading in …5
×

Introducing Dspace @ ILRI

1,774 views

Published on

Presentation by Peter Ballantyne, 1 December 2010

Published in: Technology, Design
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,774
On SlideShare
0
From Embeds
0
Number of Embeds
101
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Introducing Dspace @ ILRI

  1. 1. Introducing Dspace @ ILRI Peter Ballantyne 1 December 2010
  2. 2. CGIAR RESEARCH OUTPUTS ARE THEY TRULY ACCESSIBLE?
  3. 3. Not really … <ul><li>They are not captured </li></ul><ul><li>They are locked up behind passwords </li></ul><ul><li>They are kept inside intranets </li></ul><ul><li>They are not on the Internet, or digital </li></ul><ul><li>Their addresses are not permanent </li></ul><ul><li>They are not easy to find </li></ul><ul><li>Licenses do not encourage re-use </li></ul><ul><li>They can’t ‘travel’ as far as they should </li></ul><ul><li>.. </li></ul>
  4. 4. Who cares? Why be accessible? <ul><li>Our data information or knowledge assets should have benefits that can travel across boundaries </li></ul><ul><li>They need to be: </li></ul><ul><ul><li>Described and stored for posterity </li></ul></ul><ul><ul><li>Easily found and accessed </li></ul></ul><ul><ul><li>Easily shared and re-used </li></ul></ul><ul><ul><li>Available, accessible and applicable without restrictions </li></ul></ul>
  5. 5. AAA <ul><li>Availability - able to identify a ‘publication’ (metadata at least) </li></ul><ul><li>Accessibility – able to ‘get hold of’ the ‘whole thing’ </li></ul><ul><li>Applicability – able to adapt and re-use or re-purpose the ‘publication’ </li></ul>
  6. 6. AAA Pathways <ul><li>Promising technical and institutional routes to more or better accessibility </li></ul><ul><ul><li>Creative commons </li></ul></ul><ul><ul><li>Google </li></ul></ul><ul><ul><li>Social media </li></ul></ul><ul><ul><li>REPOSITORIES </li></ul></ul><ul><ul><li>. . . </li></ul></ul>
  7. 7. <ul><li>Repository of outputs of people and projects (hosted at ILRI) </li></ul><ul><li>Publishing and alerting platform </li></ul><ul><li>Repository for projects, institution, CRP? </li></ul><ul><li>Gateway to Google and beyond </li></ul><ul><li>Uses Dspace </li></ul>
  8. 22. Choices we made <ul><li>Organize contributions by content type (publications, multi-media, articles datasets, etc) </li></ul><ul><li>‘ Map’ items across to projects, themes, teams (organization structure – link to web sites) </li></ul><ul><li>Dublin core the basic metadata </li></ul><ul><li>FAO/AGROVOC metadata </li></ul><ul><li>Some extra ‘ILRI’ indexing (regions, subject areas – link to web sites) </li></ul><ul><li>Get many people comntributing content </li></ul>
  9. 23. Workflows <ul><li>Dspace ‘the’ ILRI way to publish on the ILRI web … </li></ul><ul><li>Projects need ‘archives’ and visibility’; Dspace offers both </li></ul><ul><li>We aim to ‘index’ everything </li></ul><ul><li>We aim to ‘publish’ as much as we can, with permission </li></ul><ul><li>We decentralise content management: Program teams contribute content; info teams do quality control </li></ul><ul><li>RSS gets content across the web and into mailboxes and desktops </li></ul><ul><li>Mainstream, open source solution, with open (OAI) standards </li></ul><ul><li>The ‘repository’ is NOT the value proposition for the scientists ; we sell it as ‘publishing’ </li></ul>
  10. 25. Future ? <ul><li>Index/make available limited access items (to the CGIAR with Active Directory?) </li></ul><ul><ul><li>Full text articles / Internal documents </li></ul></ul><ul><li>Index data and other resources, that are in full elsewhere? </li></ul><ul><li>Sign up for joint specialized support (upgrades, advanced admin and apps, look and feel, training) – http://atmire.com ? </li></ul><ul><li>A single ‘CGspace’ server (linux) for multi-users? – eg ILRI/ICRAF/CPWF … others </li></ul><ul><li>http://mahider.ilri.org / http://mahider.cgiar.org / http://dspace.waterandfood.org ?? </li></ul>

×