Contents: | Contact details: TF-Media mailing list is at <tf-media@terena.org> TERENA PDO is Peter Szegedi <szegedi@terena.org>
|
|---|
...
| Note | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||
Attendees: Eli, Vicente, Giannis, Rui, Jack, Peter Agenda:
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 professors are essential. Portal features like access to thumbnails, embedded rich media players, see what other people use, etc. are important for them. The only demonstrator 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).
|
...