This paper exists to extract from KARI’s AgriOcean Dspace history the parts of the experience that will assist other institutions in planning their individual implementations of AgriOcean Dspace or Agridrupal. It needs to be said at the outset that future implementers of AgriOcean Dspace or Agridrupal ought not to expect theirs to echo KARI’s and KAINet experience.
KAINet Portal (http://www.kainet.or.ke ): was developed using Typo3 Content Management System with WebAGRIS running in the background as the metadata management software. The KARI site was developed using Drupal and integrated with WebGRIS. On both cases user have to integrating WebAGRIS into another environment hence limiting its performance and usability. Over 30,0 metadata records and about 1,200 full-text documents are accessible on the portal.
The KAINet e-repository is continuously updated with data collected from initial participating institutions contains in the AGRIS AP XML format. A key function of KAINet is to create visibility of agricultural content by making agricultural sciences and technology documents in full-text, and associated metadata (bibliographic records) available and accessible through repositories. The institutional repositories use international methodologies, standards and web-based tools/applications for management of content.
Because limit from the previous tools and lessons learnt from the KAINet implementation there was need to look at other tools that would server the needs of the participating institutions. The KAINet ICT engaged and followed the Agridrupal and AgriOcean Dspace development and testing, offering technical inputs from time to time. AgriOcean Dspace and Agridrupal introduce into both