...
| Anchor | ||||
|---|---|---|---|---|
|
Date and Time:
Thursday, 21 February 2013 at 16.00 CET
List of participants:
Kostas, Zenon (GRNET), Vicente (UVigo), Antonio (ISEP), Eli (IUCC), Jose-Maria (RedIRIS), Peter (TERENA), and a guest speaker Sorel Reisman (California State University, MERLOT)
Notes:
- Peter (TERENA) gave a brief update on the actual status of the TERENA TF-Media OER pilot concerning the 8 open questions listed and discussed at the previous (4th technical) meeting (see above). Peter asked for a round of updates:
- Vicente (UVigo) reported that he is working together with Giannis (GRNET) to implement the 1st "proof of concept" TERENA OER system by using software components of the two corresponding projects: Campus do Mar and ARIADNE. The pilot system will use the ARIADNE aggregation engine and metadata store as well as the PuMuKit web portal front-end. The simple metadata schema will be based on both IEEE LOM (maintained by IEEE institute) and Dublin Core (maintained by Dublin Core Metadata Initiative).
- Eli (IUCC) reported that he is willing to offer a local installation of the MAOR system to be considered as the 2nd "proof of concept" TERENA OER system for comparison. Eli introduced Prof. Sorel Reisman (California State University) who will update the meeting participants about MELOR initiative in the US.
- Jose-Maria (RedIRIS) commented that he is happy to participate with the ARCA repository however, ARCA speaks RSS only. It was said that the TERENA OER system's aggregation engine should be flexible enough to speak both RSS and OAI-PMH to the local content repositories.
- Antonio (ISEP) summarized the sub-task of the pilot group as follows: 1) architecture design, 2) pilot implementation, 3) partnership. It was agreed that the pilot implementation phase needs a common understanding on the service architecture design first. The clarification of the architecture design is the highest priority, before we start selecting software tools for implementation!
- Prof. Sorel Reisman (California State University) talked about the architecture of the MERLOT (Multimedia Educational Resources for Learning and Online Teaching) system initiated by California State University in the US. It's been developing and running for 15 year now. The service community includes both academic and industry partners. MERLOT has a three levels deep layered architecture. The web portal interface is changing as we speak, trying to be much simpler (user-friendly). The metadata aggregation is using a proprietary subset of various standards. It stores and searches metadata in several languages and can turn the search results into an RSS feed. There is a federated search in about 20 libraries connected. Several web services are available (e.g., simple search, key search, etc.), some of them are for free of charge to the academic community. MERLOT is primarily a metadata repository (participants can contribute by exposing their metadata - batch input process) but there is a brand new "content builder" function of MERLOT where content can be managed.
- Peter (TERENA) commented that the TERENA OER architecture should have as modular/layered design as the MERLOT architecture has. There should not be a competition between the UVigo+GRNET vs. IUCC implementations but a potential collaboration to a common service architecture for TERENA OER. To be able to define the details/potentials of such a technical collaboration, better understanding on the actual components and functions of both the ARIADNE and MAOR systems is needed!
Agreements:
- TERENA OER must be a stand-alone OER system that does not use ARIADNE or MAOR services but builds on the (open-source) software components developed and made available by ARIADNE and MAOR projects.
- The architecture of the TERENA OER system must be modular/layered (including the aggregation engine, metadata store, and web services) preferably combining the best of the existing tools such as ARIADNE, MAOR, PuMuKit, and others.
- In order to start implementing the TERENA OER pilot, a better/deeper understanding on the actual software tools and provided functions is needed. Therefore, Peter (TERENA) calls for a small technical meeting between Eli (IUCC), Giannis (GRNET), and Vicente (UVigo) as soon as possible. The pilot group will be informed about the outcome of the technical meeting.