The document discusses plans to analyze technical requirements for integrating repositories into the Virtual Open Access Agriculture & Aquaculture Repository (VOA3R) federation. It outlines general procedures for analyzing repositories that support the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) and those that do not. It also describes plans to analyze metadata elements, formats, languages, and other attributes across repositories to homogenize metadata without losing information when integrating repositories into the VOA3R federation.

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. General Procedure Repositories with OAI-PMH Repositories without OAI-PMH Metadata analysis Why all these analyses?

3. Repositories with OAI-PMH First step is testing the OAI-PMH installation Randomly preliminary test done for Organic.Eprints, OceandDocs, slu-epsilon Needed information requested before the end of June Documents describing profile and/or usage policies for your DC Harvesting URL + Port Sets availables Name Identifier Date granularity YYYY-MM-DDThh:mm:ssZ YYYY-MM-DD Deleted records policy

4. Repositories without OAI-PMH An integration of the OAI-PMH would be necessary in order to integrate the repository in the VOA3R federation. A start point would be the installation of Dspace wich is OAI-PMH compliant (with some extra configuration) If some organization is not using a repository, an installation of DSpace will be strongly recommended. The most important issue regarding this approach is the integration of existing metadata in the new installation. Documents to be requested: Metadata schemas used, sample metadata, current retrieval intefraces for metadata

5. Metadata analysis (I) Metadata elements included in each repository Where is the location of the learning resource? Where is the identifier? Should we use a global identifier for the whole VOA3R federation? Format of each metadata element One DC:subject element for each keyword Several keywords in the same DC:subject element Dates (16/02/2010, March 2009, long time ago…)

6. Metadata analysis (II) Language support of the metadata stored in each repository to be analized Several possibilities No language information at all. Language information about the learning object itself Language information about the metadata and the learning resource itself Metadata translated in several languages for each learning resource

7. Why all these analyses? Find a way of putting all the metadata together without loosing anything Homogeneizing metadata Appliying lessons learned from Organic.Edunet