Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Definition of metadata schema for TERENA OER
  • Mechanism for metadata harvesting through OAI-PMH
  • Mechanism for OER identification
  • Mechanism for metadata transformation
  • Mechanism for metadata filtering
  • Analytics module for assessment of quality of the metadata
  • Mechanism for metadata indexing
  • REST API for searching and retrieving metadata
    Note
    title1st meeting

    Attendees: Eli, Vicente, Giannis, Rui, Jack, Peter

    Agenda:

    1. What are the SMART goals of the pilot
    2. How we are going to deliver the pilot

    Recording:

    http://emeeting.campusdomar.es/recording/838013fa539370e4d9a7d3cd3fd55361

    Notes:

    Virtual meetings will be held bi-weekly for the pilot participants. The delivery of the contracted tasks should be monitored more closely and frequently (at least weekly) by the person responsible for the delivery.

    There was a discussion whether the 9-month pilot period is okay or too short. It basically depends on the detailed objectives (SMART goals) that we want to achieve.

    The identification of the target user groups and the engagement with the professosrs are essential. Portal features like access to thumbnails, embeded rich media playrs, see what other people use, etc. are important for them.

    The only demonstartor of the OER harvesting engine back-end is the portal front-end. We need to define the most important features of the portal.

    An agile approach must be taken where we define some personas (user stories) first, mock-up a couple of portal examples, and define the back-end requirements to that.

    Users => Portal features => Metadata schema and information model => Aggregation engine

    The processing and validation of the collections (connected repositories) takes time. We also need some kind of filtering of the good quality metadata.

    Moodle LMS widgets should also be incorporated into the pilot system.

    The next coming meetings should focus on only one topic at a time to reduce discussion time. (Personas will be discussed next time).

    KIPs

     

    Indicator name progress
    ComponentExpected outcome

    Number OER content providers to be invited

    15

    Number of content providers that will share their OER through TERENA OER

    5

    Number of OERs shared through the OER TERENA portal

    10.000

    Connection with global OER initiatives e.g. GLOBE

    1

    Number of languages supported at the TERENA OER portal

    2 (EN and ES)

    Number of defined metadata compliance levels

    3 (Mandatory, Recommended, Optional)

    Dissemination activities (Presentations and publications)

    3

     

     

    TERENA OER portal
    • Free text search mechanism
    • Facet based browsing
    • Browse by topic and content type
    • OER metadata summary page
    • User login
    • Multilinguality support
    • Info graphics and images for the landing page
    • Integrate standard analytics service e.g. Google analytics
    • Latest OERs
    • Most Viewed OERs
    Metadata aggregation
    • Definition of metadata schema for TERENA OER
    • Mechanism for metadata harvesting through OAI-PMH
    • Mechanism for OER identification
    • Mechanism for metadata transformation
    • Mechanism for metadata filtering
    • Analytics module for assessment of quality of the metadata
    • Mechanism for metadata indexing
    • REST API for searching and retrieving metadata


    Indicator name

    Expected progress

    Number OER content providers to be invited

    15

    Number of content providers that will share their OER through TERENA OER

    5

    Number of OERs shared through the OER TERENA portal

    10.000

    Connection with global OER initiatives e.g. GLOBE

    1

    Number of languages supported at the TERENA OER portal

    2 (EN and ES)

    Number of defined metadata compliance levels

    3 (Mandatory, Recommended, Optional)

    Dissemination activities (Presentations and publications)

    3

    Component

    Expected outcome

    TERENA OER portal

    • Free text search mechanism
    • Facet based browsing
    • Browse by topic and content type
    • OER metadata summary page
    • User login
    • Multilinguality support
    • Info graphics and images for the landing page
    • Integrate standard analytics service e.g. Google analytics
    • Latest OERs
    • Most Viewed OERs

    Metadata aggregation