E. Kaldoudi – DUTH

Deliverable 1.2: Study Report on Content Sharing

Functional Requirements

3rd Project Meeting Plovdiv, Bulgaria

, 21-23 January 20101

Deliverable 1.2

title: Study report on content sharing functional requirements

within WP1: project start up

output of actions:

− A.1.6: Compose functional description and desired functionalities for the sharing of content

− A.1.2: Identify and describe partners’ LCMSs and related infrastructure

related milestone: M.1.2: Functional requirements for medical educational content sharing have been layed out. (Month 4)

Mallorca, 2nd Project Meeting, 27-29 September, 20092

D.1.2 details and status

3 Mallorca, 2nd Project Meeting, 27-29 September, 2009

dissemination level PP – restricted to programme participants

delivery date 15th October 2009

authorsE. Kaldoudi, A. Antoniades, C. Schizas, C. Pattichis, P. Bamidis

status submitted and approved

total no. of pages 170 (including 2 Appendices)

total no. of words ~41.000

D.1.2. contents

1. Introduction

2. The mEducator Concept

3. Survey on Functional Requirements

4. mEducator Functional Requirements

5. Further Refinement of Functional Requirements

6. References

Appendix A. Survey on Functional Requirements

Appendix B. Partners’ LCMS & Related Infrastructure

4 E. Kaldoudi - DUTHMallorca, 2nd Project Meeting, 27-29 September, 2009

1. Introduction

– the goal is to present overall desired functionality by a

potential mEducator environment, including a deeper

analysis of principal concepts and notions described in DoW

– D.1.2 is expected to act as a guide for the description of

metadata scheme

– the overall functionality presented here will be fine-tuned via

usage scenarios for each of the two different solutions (WP4

& WP5)

Mallorca, 2nd Project Meeting, 27-29 September, 20095

2. The mEducator Concept

the project aims to research towards an infrastructure for

sharing educational content over the web.

– the final environment does NOT aim to own educational

content, nor to lend educational content, not to lease

educational content, neither to distribute educational content.

– the final environment does NOT aim to provide learning and

course management as in a learning management system

does

Mallorca, 2nd Project Meeting, 27-29 September, 20096

2. The mEducator Concept (cnt.)

– the final environment aims to create the necessary

infrastructure for interested parties to freely exchange their own

educational content, that itself resides somewhere on the web

– the actual content repositories and/or webpages are not necessarily part of the environment

– content, when discovered and retrieved via mEducator, can be

used in a variety of ways, for example it can be incorporated

within a learning management system (which again is not part

of the mEducator environment

7

2. The mEducator Concept (cnt.)

– the actual content and it IPR remains with the author (or as

stated by the IPR)

– the final environment only deals with metadata

links/pointers to the content and all the necessary

mechanisms to make this content search meaningful, user

friendly, customizable, scalable and expandable, while

providing support for content quality assurance, content

IPR resolution, and social networking of content authors

and content consumers

8

3. The mEducator Content

– content definition (see also D.3.1)

– content sources

– content types

– repurposed content

– mEducator goals for different users: academic teachers,

students, healthcare professionals, professional content

providers, the public

Mallorca, 2nd Project Meeting, 27-29 September, 20099

3. Survey on Functional Requirements

as presented earlier this morning …

Mallorca, 2nd Project Meeting, 27-29 September, 200910

4. Functional Requirements

1. publishing content on mEducator

provide a description based on the mEducator

metadata scheme and a URI for the location of the

content item

ability to update the above

record original metadata and versions

metadata should highlight the educational facet of the

item

Mallorca, 2nd Project Meeting, 27-29 September, 200911

4. Functional Requirements

2. repurposed content

metadata to describe repurposing and IPR

3. content organization

support both approaches: taxonomy and folksonomy

4. content search

5. feedback on content

ability for users to provide feedback: review, annotate,

discuss, rate, etc

Mallorca, 2nd Project Meeting, 27-29 September, 200912

4. Functional Requirements

6. content quality issues

provision for authoritative quality stamp as well as peer rating

and voting

7. content IPR issues

open access but not without conditions

adopt Creative Commons copyright policies for users to

choose from

8. language

automatic translation of metadata

13

4. Functional Requirements

9. content sharing model

basically free

explore a model of credits based on participation (CME 2.0)

10. social networking and other added value functionalities

11. personalization/customization

create, manage, share one’s own collections, etc

12. links to prerequisites on how to use content

wiki like based, collaboratively developed

14

4. Functional Requirements

13. user support content sharing model

wiki like based, collaboratively developed

14. extending the environment

allow for extensions, plug-ins, etc.

provide for links to standard educational/certification

procedures

15. content repository (optional)

16. user engagement and administration

15

5. Further Refinement of Requirements

– in WP4 and WP5

Mallorca, 2nd Project Meeting, 27-29 September, 200916

APPENDICES

– A – Survey results

– B – Partners ’infrastructure

Mallorca, 2nd Project Meeting, 27-29 September, 200917

partner LCMS other related infrastructure

AUTH Moodle 1.9.2+c (Build: 20081011) semantic wiki

OpenLabyrinthUCY Moodle

DUTH Moodle 1.9.3+ (Build: 20090107)

SITUSI -- MEDTING platform

UTCN YES eTrace

UNS Plone/Zope (Jalon 2.6 r0608)

MUPLOVDIV -- general use of web technology

UNICT -- Web-Trace 2.0

UH Moodle 1.9 Apumatti

SGUL OpenLabyrinth

CU CU online Moodle18