Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Voa3r Identification Analysis Technical Requirements


Published on

Identification of the technical requirements in the VOA3R project

Published in: Education, Technology
  • Be the first to comment

  • Be the first to like this

Voa3r Identification Analysis Technical Requirements

  1. 1. KickOff Meeting, 09/06/2010, Athens, Greece VOA3R V irtual O pen A ccess A griculture & A quaculture R epository: sharing scientific and scholarly research related to agriculture, food, and environment Method for identification/analysis of technical requirements
  2. 2. General Procedure <ul><li>Repositories with OAI-PMH </li></ul><ul><li>Repositories without OAI-PMH </li></ul><ul><li>Metadata analysis </li></ul><ul><li>Why all these analyses? </li></ul>
  3. 3. Repositories with OAI-PMH <ul><li>First step is testing the OAI-PMH installation </li></ul><ul><ul><li>Randomly preliminary test done for Organic.Eprints, OceandDocs, slu-epsilon </li></ul></ul><ul><li>Needed information requested before the end of June </li></ul><ul><ul><li>Documents describing profile and/or usage policies for your DC </li></ul></ul><ul><ul><li>Harvesting URL + Port </li></ul></ul><ul><ul><li>Sets availables </li></ul></ul><ul><ul><ul><li>Name </li></ul></ul></ul><ul><ul><ul><li>Identifier </li></ul></ul></ul><ul><ul><li>Date granularity </li></ul></ul><ul><ul><ul><li>YYYY-MM-DDThh:mm:ssZ </li></ul></ul></ul><ul><ul><ul><li>YYYY-MM-DD </li></ul></ul></ul><ul><ul><li>Deleted records policy </li></ul></ul>
  4. 4. Repositories without OAI-PMH <ul><li>An integration of the OAI-PMH would be necessary in order to integrate the repository in the VOA3R federation. </li></ul><ul><li>A start point would be the installation of Dspace wich is OAI-PMH compliant (with some extra configuration) </li></ul><ul><li>If some organization is not using a repository, an installation of DSpace will be strongly recommended. </li></ul><ul><li>The most important issue regarding this approach is the integration of existing metadata in the new installation. </li></ul><ul><li>Documents to be requested: Metadata schemas used, sample metadata, current retrieval intefraces for metadata </li></ul>
  5. 5. Metadata analysis (I) <ul><li>Metadata elements included in each repository </li></ul><ul><ul><li>Where is the location of the learning resource? </li></ul></ul><ul><ul><li>Where is the identifier? </li></ul></ul><ul><ul><li>Should we use a global identifier for the whole VOA3R federation? </li></ul></ul><ul><li>Format of each metadata element </li></ul><ul><ul><li>One DC:subject element for each keyword </li></ul></ul><ul><ul><li>Several keywords in the same DC:subject element </li></ul></ul><ul><ul><li>Dates (16/02/2010, March 2009, long time ago…) </li></ul></ul>
  6. 6. Metadata analysis (II) <ul><li>Language support of the metadata stored in each repository to be analized </li></ul><ul><li>Several possibilities </li></ul><ul><ul><li>No language information at all. </li></ul></ul><ul><ul><li>Language information about the learning object itself </li></ul></ul><ul><ul><li>Language information about the metadata and the learning resource itself </li></ul></ul><ul><ul><li>Metadata translated in several languages for each learning resource </li></ul></ul>
  7. 7. Why all these analyses? <ul><li>Find a way of putting all the metadata together without loosing anything </li></ul><ul><li>Homogeneizing metadata </li></ul><ul><li>Appliying lessons learned from Organic.Edunet </li></ul>