Presented by Peter Ballantyne and Abenet Yabowork at Dspace Ethiopia Interest Group Meeting and Training, Addis Ababa, Ethiopia, 28 October – 1 November 2013.
1. Using Dspace @ ILRI
Peter Ballantyne and Abenet Yabowork
Dspace Ethiopia Interest Group Meeting
Addis Ababa, 28 October 2013
2. Dspace at ILRI
• Established late 2009
• Driven by demands to have all outputs and products available
and accessible
• Replacement for:
Inmagic document catalogue
PDF files spread across the web site
Home made lists of outputs
Manual linking from web sites and blogs etc
• Evolved into ‘CGSpace’ in 2011
4. Why be accessible?
Our data information or knowledge assets should have benefits
that can travel across boundaries
They need to be:
Described and stored for posterity
Easily found and accessed
Easily shared and re-used
Available, accessible and applicable without restrictions
5. • Repository of outputs of people and projects (hosted at
ILRI)
• Publishing and alerting platform
• Repository for projects, institutions, programs …
• Gateway to Google and beyond
• Uses Dspace
• [dec 2010 slide]
6. •
•
•
•
•
•
•
•
•
•
Dspace ‘the’ ILRI way to publish on the ILRI web …
Gives projects ‘archives’ and visibility’
We aim to ‘index’ everything, wherever published
We aim to ‘publish’ as much as we can, with permission
We decentralise content management: Program teams contribute
content; info teams do quality control
RSS gets content over the web and into mailboxes and onto desktops
Mainstream, open source solution, with open (OAI) standards and
wide support community
The ‘repository’ is NOT the value proposition for the scientists ; we
sell it as ‘publishing’
It does NOT do all ‘library’ tasks
Part of ‘being open’
7. Content choices we made
• Organize contributions by content type
(publications, multi-media, articles
datasets, etc)
• ‘Map’ items across to projects, themes, teams
(organization structure – link to web sites)
• Dublin core the basic metadata
• Several ‘extra’ fields (regions, subject
areas, CRPs)
• Get many people contributing content (a few
editors)
12. What is ‘CGSpace’
‘Multi-tenant’ use of a Dspace application
Shared admin, look and feel, publishing, content
management, hosting, training, support
Shared hosting, development, and learning [and server]
Allows searching across collections
13. CGSpace: Repository of Agricultural Research Outputs
Publications, journal articles, books, training materials,
project reports, factsheets and links to digital audios,
videos, presentations and posters
Hosted content
Content ‘out’
Harvested content
open access + open standards + open licenses
=
enhanced visibility of research outputs
30. Running ‘CGSpace’
•We aim for are ‘cost-’ and ‘expertise’-sharing
•Requires ‘more than basic’ expertise to exploit in
terms of admin, customization, interface, content
architecture
•All code changes deposited in GIThub [where main
dspace code development now is]
•Active yammer network
•15% of a linux admin person at ILRI
•80% of a information systems person
•Dedicated linux server at CGNET
•? % of content specialists
31. Ongoing work
• ILRI content migration from inmagic
• SSSL and LDAP [to allow AD synchronization]
• @mire metrics and reporting modules
• @mire training
• Discovery module
• Dspace to wordpress
• Dspace to drupal
• Dspace - dataverse
• AGROVOC plugin
• Harvest from other Dspaces
• Look and feel/item presentation
32. Challenges
• Repository structure to org structure
• Dspace management
• Server and backend management
• Quality assurance
• …
• ‘Publishing’ v ‘library’
• Support to scale up
33. Better lives through livestock
ilri.org
The presentation has a Creative Commons licence. You are free to re-use or distribute this work, provided credit is given to ILRI.