ERASMUS’PLUS’2015’ SECTORSKILLS’ALLIANCES’ · 2017-10-26 · Deliverable’5.1.2’ ’ 562634=EPP=1=2015=IT=EPPKA2=SSA’ ’’CARESS’Project’ ’3’of’45’ ’

ERASMUS PLUS 2015 SECTOR SKILLS ALLIANCES

AGREEMENT No. 2015 – 3212 / 001 – 001

PROJECT No. 562634-‐EPP-‐1-‐2015-‐IT-‐EPPKA2-‐SSA

Deliverable Number: 5.1.2

Title of Deliverable: Integration of Virtual Communities of Practice (VCP) Platform (version 2) with e-‐Learning Platform

WP related to the Deliverable: 5

Dissemination Level: (PU/PP/RE/CO)*: PU

Nature of the Deliverable: (R/P/D/O)**: R

Actual Date of Delivery to the CEC: 15/9/2017

PARTNER responsible for the Deliverable: UVA

WP starting month M16

WP ending month M36

Partner Contributor(s): GGallery, Si4Life, UVA

Partner Reviewer(s):

*Dissemination Level:

PU=Public

CO=Confidential, only for members of the Alliance (including Commission Services).

PP=Restricted to external subjects in confidential mode (including Commission Services)

RE=Restricted to a group specified by the Alliance (including Commission Services).

**Nature of Deliverables:

R=Report

P=Prototype

D=Demonstrator

O=Other

Deliverable 5.1.2

562634-‐EPP-‐1-‐2015-‐IT-‐EPPKA2-‐SSA CARESS Project 2 of 45

ABSTRACT This report provides a technical description of the second version of the web-‐based platform for supporting the CARESS Virtual Community of Practice (VCP). The vision for a CARESS VCP was unfolded in deliverable D3.6 (VCP – environment conceptual design), based on an analysis of the state of the art in Healthcare-‐related VCPs, as well as on internal discussions among domain experts participating in the project. D3.6 defined a first set of use cases that identify the functional requirements of the VCP platform. A first version of the VCP platform was developed and reported in D5.1.1. The second version of the VCP platform, reported in this document, includes improved functional features for supporting the certification of competences in non-‐formal/informal learning contexts, as well as architectural modifications for its integration with the E-‐learning platform that has been developed within T4.1 (and reported in D4.1.1).

KEYWORDS CARESS Virtual Communities of Practice (VCP), VCP Platform, CARESS VCP use cases, Non-‐formal/Informal Competence Recognition, Integration with e-‐Learning Platform.

LIST OF BENEFICIARIES (PP-‐RE)/PARTICIPANTS (PU-‐CO)*** Ben. No. Beneficiary Name Short Name Country

1 Si4Life – Scienza e Impresa Insieme per Migliorare la Qualità della Vita s.c.r.l.

Si4Life Italy

2 Regione Liguria Liguria Region Italy

3 Ggallery s.r.l. GGallery Italy

4 I.T.C. “Vittorio Emanuele II-‐Ruffini” VE-‐II Italy

5 AGE-‐Platform AGE Belgium

6 OMNIA OMNIA Finland

7 Finnish National Board of Education FNBE Finland

8 Super SUPER Finland

9 Ayuntamiento de Valladolid AYTO Spain

10 Universidad de Valladolid UVA Spain

11 Sociedad de Geriatría y Gerontología de Castilla y León SGGCYL Spain

12 Associazione Polo Tecnico Professionale Professioni Vita Pro. Vi Hub Italy

13 Azienda Regionale Sanitaria Ligure ARS Italy

14 Royal Cornwall Hospitals Trust RCHT UK

15 United Kingdom Homecare Association UKHCA UK

16 Nestor Primecare Services Ltd – Allied Healthcare Allied Healthcare UK

Deliverable 5.1.2


*** List of Beneficiaries

In case of dissemination level PU or CO please indicate all the partners involved in this Deliverable.

In case of dissemination level PP please indicate the names of the other subject to whom the deliverable is devoted

In case of dissemination level RE please indicate the restricted group of partners.

VERSION HISTORY and AUTHORS

VERSION PRIMARY AUTHOR VERSION DESCRIPTION DATE COMPLETED

1 Javier E. Hoyos-‐Torío (UVA) Juan I. Asensio-‐Pérez (UVA)

Deliverable structure and draft content

26/05/2017

2 Javier E. Hoyos-‐Torío (UVA) Juan I. Asensio-‐Pérez (UVA) Serena Alvino (Si4Life)

Feedback from Si4Life and GGallery integrated

15/09/2017

Deliverable 5.1.2


Table of Contents ABSTRACT .......................................................................................................................................................... 2

KEYWORDS ........................................................................................................................................................ 2

LIST OF BENEFICIARIES (PP-‐RE)/PARTICIPANTS (PU-‐CO)*** ............................................................................. 2

VERSION HISTORY and AUTHORS ...................................................................................................................... 3

Table of Contents .............................................................................................................................................. 4

1 INTRODUCTION: STRUCTURE AND AIMS OF THE DOCUMENT ................................................................. 5

2 SUPPORTING THE RECOGNITION OF COMPETENCES IN NON-‐FORMAL/INFORMAL LEARNING CONTEXTS 6

2.1 Tracking report’s use cases .............................................................................................................. 7 2.1.1 Export tracking data .................................................................................................................... 7

2.2 Experience diary’s use cases ............................................................................................................ 9

2.2.1 Create a diary entry ..................................................................................................................... 9

2.2.2 Edit a diary entry ....................................................................................................................... 13

2.2.3 Export Experience Diary ............................................................................................................ 16

3 INTEGRATION WITH THE E-‐LEARNING PLATFORM .................................................................................. 18

3.1 Use case dealing with the register into the VCP/e-‐Learning Platforms ......................................... 19

3.1.1 Register for an account in the VCP/e-‐Learning Platforms ......................................................... 19

3.2 Use cases dealing with the integration of the VCP Platform and the e-‐Learning Platform ........... 27

3.2.1 Get the list of courses in the e-‐Learning platform ..................................................................... 27

3.2.2 Get the list of courses in the e-‐Learning platform in which the user is enrolled ....................... 29

3.2.3 Enrol the user in a course of the e-‐Learning platform ............................................................... 32

3.2.4 Unenrol the user from a course of the e-‐Learning platform ..................................................... 35

3.2.5 Cancel request to enrol the user in a course of the e-‐Learning platform .................................. 37

3.2.6 View the topics and content of a course of the e-‐Learning platform ........................................ 39

3.2.7 Accessing a course of the e-‐Learning platform .......................................................................... 42

4 CONCLUSIONS ......................................................................................................................................... 44

5 REFERENCES ............................................................................................................................................ 45

Deliverable 5.1.2


1 INTRODUCTION: STRUCTURE AND AIMS OF THE DOCUMENT1 WP5 has the ultimate goal of supporting the non-‐formal and informal learning components of the CARESS national pilots. CARESS proposes doing so by setting up and nurturing Virtual Communities of Practice (VCP). A Community of Practice is a “group of people who share a common concern, a set of problems, a set of problems, or a passion about a topic, and who deepen their knowledge and expertise in this area by interacting on an ongoing basis” [1, pp. 4]. A VCP adds to Communities of Practice the ICT support for enabling additional means for interaction, remotely and asynchronously through the Internet. The role of VCPs in the non-‐formal and informal learning aspects of the CARESS pilots has been defined in deliverable D3.6 (“VCP-‐ environment conceptual design”) [2]. That deliverable also explains the relationships of the VCP with the e-‐Learning platform that is being developed within the context of WP4. Additionally, D3.6 explains the need for task 5.2 (“Supporting and feeding Virtual Communities of Practice”), since it is well reported in the literature the difficulties for making VCPs sustainable in the long-‐term. Figure 1 (from [2]) explains graphically these relationships among CARESS tasks.

Figure 1. Connections among tasks concerning VCPs (from D3.6 [2])

Deliverable D5.1.1 [3] reported the preliminary work within task T5.1 (“Development of VCP Platform and integration with the e-‐Learning platform): it discussed the technical alternatives for the development of the CARESS VCP Platform; it described the high-‐level software architecture of the Platform; and, it illustrated how the developed prototype supported the VCP Platform use cases proposed in D3.6 [2].

Since the delivery of D5.1.1 in month M19, feedback from CARESS Partners about the first prototype has triggered some functional improvements in the current prototype, mostly related with the support to the recognition of competences in the non-‐formal/informal learning contexts that the VCP Platform is intended to enable. These improvements will be reported in this document. Additionally, a first prototype of the e-‐Learning platform, aimed at scaffolding the formal online parts of the CARESS pilots, has been developed and set up (task T4.1, deliverable D4.1.1 “Customized e-‐Learning Platform”). According to the CARESS work plan, the CARESS VCP and e-‐Learning Platforms should be integrated to ease the transition of Health Home Care Practitioners (HHCP) from formal to non-‐formal/informal learning contexts. This document will detail the technical aspects of the integration that has been carried out, as well as the resulting developed prototype that will support the piloting phase of the project. The prototype is ready to support the three languages of the planned pilots (Finnish, Italian and Spanish) thanks to the multilingual features of the Easysocial Joomla! Add-‐on on which the CARESS VCP Platform is based [3].

1 With the aim of making this document self-‐contained, part of this introductory section is the same than that of deliverable D5.1.1 [1].

Deliverable 5.1.2


2 SUPPORTING THE RECOGNITION OF COMPETENCES IN NON-‐FORMAL/INFORMAL LEARNING CONTEXTS

According to D3.6 [2] the CARESS VCP Platform will support non-‐formal and informal learning recognition by 2 main types of tools and functionalities:

• Users tracking functionalities: the participation of a member in a VCP will be tracked automatically by the system; information such as number and duration of the connections, visited areas, uploaded documents, messages sent (number and contents), participation in virtual meetings, etc. will be available on the platform; these data could be exported in standard formats; the export of these data could be managed directly by the user (VCP member) in order to get information which could be provided to the competent authorities (to teachers for instance) to support competence recognition; a detailed list of tracking data which will be available on the platform has been defined in collaboration with T6.2 [4] (Evaluation and monitoring plan) activities (see Figure 2 below).

Figure 2. Tracking data to gather from the VCP Platform (obtained from [4]).

• VCP experience diary: this tool will allow for a personal description of the user experience as a

member of the VCP; it will be managed directly by the VCP member who could choose, among the other functionalities of the platform, to fill-‐in periodically a diary where he/she could describe his/her own experience in the VCP (activities, discussions, lesson learnt, created contacts, etc.); this tool will provide questions/suggestions/hints for the textual description of the personal experience, in specific sections or chapters; the chronological versioning of the resulting diary should be tracked and presented in the final output someway; the user will be able to export the diary anytime, in a user-‐friendly format.

The following subsections showcase how the abovementioned requirements have been implemented in the second prototype of the VCP Platform (http://communitycaress.gsic.uva.es).

Deliverable 5.1.2


2.1 Tracking report’s use cases 2.1.1 Export tracking data

Brief description

The system will generate an activity record of the main actions carried out by the user while using the Virtual Community of Practice Platform. The gathered information, that is, the tracking data, can be exported by the user as a PDF file. This way, that data could be used for competence recognition purposes.

Preconditions

The user is logged in the Virtual Community of Practice.

Postconditions

The tracking data is exported as a PDF file.

Flow of events

1. The user clicks on the “Tracking report” menu entry of the “Main Menu”, which is located at the right side of the Virtual Community of Practice’s site. This menu entry is only visible when the user is already logged in the Virtual Community of Practice.

Deliverable 5.1.2


2. The system shows an ordered by date record with the main actions made by the user while using the Virtual Community of Practice. This information includes, for each action recorded, the action type, and the date and hour in which the action happened.

The user clicks on the button “Export Tracking data” to export the Tracking data as a PDF file. The document is opened in a new tab in the browser. This document starts with a table of contents. The first chapter describes the aim of the document and information about the Virtual Community of Practice’s user from whom the tracking data has been gathered. The second chapter contains the tracking indicators. There is a subchapter for each group of tracking indicators that have been taken into account (upload content, posting actions, event actions, group actions, Experience Diary’s actions and Actions in each group). The information is displayed by means of tables that, for each action, indicate how many times it has been carried out by the user in the Virtual Community of Practice or within a group of the virtual Community of Practice that he/she moderates or is a member of.

Deliverable 5.1.2


2.2 Experience diary’s use cases

2.2.1 Create a diary entry

Brief description

A user wants to describe his/her personal experience as a member of the Virtual Community of Practice. In order to do that, the user can create periodically a new entry in his/her experience diary. This personal experience can include the activities he/she carried out, the discussions in which he/she took part, those lessons learnt by the user, the created contacts and so on.

Preconditions


Postconditions

The new diary entry has been added to the user’s Experience diary.

Flow of events

1. The user clicks on the “Experience diary” menu entry of the “Main Menu”, which is located at the right side of the Virtual Community of Practice’s site home web page. This menu entry is only visible when the user is already logged in the Virtual Community of Practice.

Deliverable 5.1.2


2. There are no diary entries yet. Otherwise, these diary entries would be displayed at the bottom of the page. The user clicks on the “New Diary Entry” button to add a new entry in his/her Experience diary.

The user can select a pre-‐created template to write the diary entry from those available in the platform. A template is made up of several sections. Moreover, every section in a template can include questions or suggestions to make it easier for the user to enter the textual description of his/her personal experience in the Virtual Community of Practice. A diary entry always refers to a specific period of time. It is also possible for the site administrator to edit these templates or add new ones to the platform.

The user chooses the “template for Diary Entry” by clicking on its image. This template is intended to help the user create a diary entry by means of predefined questions for a set of sections.

Deliverable 5.1.2


3. The template to be filled out is displayed then. This template has some questions or suggestions for

each section. The template also requests information about the period of time the diary entry describes.

Deliverable 5.1.2


4. The user fills out the template before publishing the diary entry. It is also possible to choose a category for the diary entry. Finally, the user clicks on the button “Publish Diary Entry” to make it published. Once published, the diary entry will appear with the other diary entries.

5. A success message is displayed. The user clicks on the button “Back” to go back to the Experience

diary and get the updated list of diary entries.

Deliverable 5.1.2


6. The list of diary entries includes the just created entry. The user can search for diary entries by its

name or filter them by category or state.

2.2.2 Edit a diary entry

Brief description

Deliverable 5.1.2


A user wants to edit a diary entry that describes his/her personal experience as a member of the Virtual Community of Practice. This personal experience can include the activities he/she has carried out, the discussions in which he/she took part, those lessons learnt by the user, the created contacts and so on.

Preconditions


There are diary entries.

Postconditions

The diary entry is updated in the Experience diary.

Flow of events

1. The user clicks on the “Experience diary” menu entry of the “Main Menu”, which is located at the right side of the Virtual Community of Practice’s site. This menu entry is only visible when the user is already logged in the Virtual Community of Practice.

2. The list of diary entries is not empty. The user clicks on the name of the diary entry he/she wants to edit. The user clicks on “My first week as a member of the VCP” in order to edit that diary entry. The editor is displayed and the user modifies the content of the diary entry. Finally, the user clicks on the “Update Diary Entry” in order to update the published Diary Entry on the site.

Deliverable 5.1.2


3. A success message is displayed on the site. The user clicks on the button “Back” to go back to

the Experience diary and gets again the list of diary entries.

4. The list of diary entries includes the updated diary entry.

Deliverable 5.1.2


2.2.3 Export Experience Diary

Brief description

A user that has described his/her personal experience as a member of the Virtual Community of Practice wants to export his/her Experience Diary. This Experience Diary contains all of the diary entries, each of them including the activities he/she carried out, the discussions in which he/she took part, those lessons learnt by the user, the created contacts and so on, as a PDF file.

Preconditions


Postconditions

The Experience diary is exported as a PDF file.

Flow of events

1. The user clicks on the “Experience diary” menu entry of the “Main Menu”, which is located at the right side of the Virtual Community of Practice’s site. This menu entry is only visible when the user is already logged in the Virtual Community of Practice.

Deliverable 5.1.2


2. The user clicks on the “Export diary” button to export the Experience Diary as a PDF file. The document is opened in a new tab in the browser. The document starts with a table of contents. The first chapter contains the information about the Experience Diary’s Author. The second chapter contains the list of Diary Entries. For each diary entry, the information provided in the report includes its title, category, creation date, last modified date, author and textual content.

Deliverable 5.1.2


3 INTEGRATION WITH THE E-‐LEARNING PLATFORM2 In order to facilitate the transition of HHCPs from formal to non-‐formal/informal learning, CARESS WP5 proposes the integration of the e-‐Learning Platform with the VCP Platform being developed in task T5.1. Since the VCP Platform is an extension of the Joomla! (https://www.joomla.org/) Content Management System and since the e-‐Learning Platform is built on top of Moodle, the integration of both platform has been based on the Joomdle (https://www.joomdle.com/) open-‐source product. The integration based on Joomdle provides several advantages from the CARESS point of view:

2 Most of the contents of this section also appears in deliverable D4.1.1. They are included here to make this document self-‐contained.

Deliverable 5.1.2


• It supports a single sign-‐on authentication schema. This way, HHCPs can log in once (e.g., in the VCP Platform) and access both Platforms seamlessly.

• It allows centralized user profiles. This way, a HHCP updating his/her profile in the VCP Platform will get his/her profile automatically updated in the e-‐Learning Platform.

• It allows the access and the visualization of content from the e-‐Learning Platform in the VCP Platform, thus facilitating the reuse of e-‐Learning material in non-‐formal/informal learning activities.

The use of Joomdle facilitates “the integration of both platforms in a unique “meeting point” for HHCPs participating in both formal, informal and non-‐formal learning activities”, as requested by the CARESS work plan. As a consequence of this approach, the VCP/e-‐Learning Platform will be provided to the users as an integrated system. The users will typically use the VCP address (http://communitycaress.gsic.uva.es) for accessing both platforms, although users enrolled in e-‐Learning courses can still use the address http://elearningcaress.gsic.uva.es (see D4.1.1) for directly accessing the e-‐Learning Platform, if desired.

The integration of the VCP and e-‐Learning Platforms is expected to evolved throughout three “stages” during the lifetime of the project (and beyond) in relation to their “users” (i.e., trained HHCPs). In a nutshell:

• STAGE 1 (during CARESS pilots): in this stage users of the two Platforms will be the same (participants in e-‐Learning courses will be able to access de VCP seamlessly and vice versa). It is expected that teachers of the pilots will provide the administrators of the platforms with a list of students to enrol in the pilot courses. Thanks to the Joomdle-‐based integration, these students will become automatically members of the CARESS VCP.

• STAGE 2 (after pilots, before the end of the project): some of the pilot students will become “senior members”/moderators in the VCP, but will remain students in the e-‐Learning platform. Meanwhile, the VCP will be opened to the public and the e-‐Learning platform will still be under the control of the CARESS partners. New HHCPs joining the CARESS VCP will be automatically enrol in the e-‐Learning Platform as students, but they will not be enrolled in the e-‐Learning courses of the pilots (new e-‐Learning courses might eventually be created and the newcomers to the VCP might ask for their enrolment in those courses).

• STAGE 3 (after the end of the project): both the VCP Platform and the e-‐Learning Platform will be active for at least one year after the end of the project. It is expected that the VCP will be self-‐sustained and under the control and initiative of VCP senior members. The policy for the management of the e-‐Learning Platform will be decided at the end of the project lifetime.

3.1 Use case dealing with the registration into the VCP/e-‐Learning Platforms

3.1.1 Register for an account in the VCP/e-‐Learning Platforms

Brief description

The user wants to register for an account in the platform in order to become a member of the Virtual Community of Practice (thanks to the integration provided by Joomdla, s/he will become automatically a student of the e-‐Learning Platform, although s/he cannot enter any of its courses until s/he is enrolled by a teacher/instructor, as explained at the beginning of this section).

Preconditions

No preconditions are required.

Deliverable 5.1.2


Postconditions

The user is registered in the VCP with the role of “Community member”.

The user is registered automatically in the E-‐learning platform with the same credentials.

Flow of events

1. The user opens the Web browser and enters the VCP Platform’s URL (https://communitycaress.gsic.uva.es). The home page is loaded. Since the user does not have an account yet, he/she clicks on the “Register for an Account Today” button in order to start the registration process.

2. The registration process has three steps. In the first step the user has to provide the platform with the basic information about the account. There are several mandatory fields such as the Name, the username in the VCP/e-‐Learning Platform, a password and a valid email address. Besides, the user can choose the language to use throughout the site (English, Spanish, Italian or Finnish).

Deliverable 5.1.2


3. The user is also requested to provide the platform with some more. For instance, the gender and

the birthday are required. There are some other optional fields for extra information. Once the user has filled in all of the fields marked as required, he/she clicks on the “Continue” button.

Deliverable 5.1.2


4. The second step in the registration process is about the education background and profession of the user. The user has to provide the platform with information about the university or college he/she studied at. The user can indicate what their bachelor’s degree is and which year he/she graduated. Additionally, the user is requested to provide information about the type of Home Health Care Professional s/he is and in which country s/he is currently working in. There are nine types of HHCPs. When the user hovers the mouse over an HHCP type, a tooltip with an explanatory definition for the HHCP is displayed for that option. Once the user has entered that information, s/he clicks on the “Continue” button.

Deliverable 5.1.2


5. The last step in the registration process is “appearance”. It lets the user customize how his/her profile will look like to other users. The user can upload a profile picture and a profile cover. Once finished, the user clicks on the “Submit” button.

6. A message is displayed to the user to inform him/her that account has to be approved by a moderator. Once it is approved, the user should receive an email notification in his email account.

7.

Deliverable 5.1.2


a) The site administrator receives an email indicating that a new user has been registered on the Virtual Community of Practice and their account requires his/her approval. He/she can use the links provided in the email to reject or approve the user.

b) The administrator can also check the list of users who are registered on the site but whose registrations are still pending approval by clicking on the menu item Components-‐>EasySocial-‐>Users. Then he/she clicks on the “Pending Approvals” link.

If the site administrator clicks on the user, he/she can view the user’s profile. Therefore, he/she can check the basic information, the education and appearance fields that were filled in by the user in the registration process

Deliverable 5.1.2


.

If the site administrator wants to approve the account, he/she clicks on the “Approve” button. Otherwise, he/she clicks on the “Reject” button. Then, he/she is requested to confirm the action and can enable the option of sending a confirmation email to the recipients.

Once approved, a success message is showed.

8. Now, the user can login in the Virtual Community of Practice/e-‐Learning Platform. He/she goes to the home page of the Virtual Community of Practice (https://communitycaress.gsic.uva.es). Then, he/she enter their username and password in the login form and clicks on the “Log Me in” button.

Deliverable 5.1.2


9. The user can start using the platform. As it is the first time that he/she logs in, a welcome message is showed.

Deliverable 5.1.2


10. Since the user has been also automatically registered in the e-‐Learning platform, he/she could use the same credentials to login there (https://elearningcaress.gsic.uva.es) later on. Moreover, once logged in the VCP, if the user clicks on the “e-‐Learning Platform” menu entry, which is available in the “Main Menu”, he/she is automatically logged in the e-‐Learning platform too. A new tab is opened in the browser to let the user manage their e-‐Learning platform’s account. The user is not automatically enrolled in any of the available courses in the e-‐Learning platform.

3.2 Use cases dealing with the integration of the VCP Platform and the e-‐Learning Platform

3.2.1 Get the list of courses in the e-‐Learning platform

Brief description

A member of the Virtual Community of Practice wants to get the list of courses that are available in the e-‐Learning platform without leaving the VCP.

Preconditions

The user is registered in the e-‐Learning platform.

The user is logged in the Virtual Community of Practice (a user registered in the e-‐Learning platform is automatically registered in the VCP platform).

Flow of events

Deliverable 5.1.2


1. The user clicks on the “Course list” menu entry of the “e-‐Learning Platform Menu” which is located at the right side of the Virtual Community of Practice site.

2. The list of available courses grouped by course category is displayed. For each course in the e-‐Learning platform, its title is showed.

3. Since the user wants to know more about the “Dementia” course, s/he clicks on its title. Some information about the course is showed then: the course category, a summary, the due start date, the number of topics, and so on. The user can also see more detailed information about the course topics or the course content (see the use case “See the course content”). Besides, depending on

Deliverable 5.1.2


his/her status in the course (unenrolled, the enrol request is still pending to be accepted or the enrol request was rejected), some actions might be available (request to enrol in a course, cancel a request, unenrol from the course or go to the course).

3.2.2 Get the list of courses in the e-‐Learning platform in which the user is enrolled

Brief description

A member of the Virtual Community of Practice wants to get the list of courses in the e-‐Learning platform in which he/she is enrolled without leaving the VCP.

Preconditions



Flow of events

1. The user clicks on the “My Course list” menu entry of the “e-‐Learning Platform Menu” which is located at the right side of the Virtual Community of Practice site.

Deliverable 5.1.2


2. The list of courses in which the user is already enrolled, grouped by course category, is displayed. For each course in the e-‐Learning platform, its title is showed.

Deliverable 5.1.2


3. Since the user wants to see more about the content “Primary Care” course in which s/he is already

enrolled, clicks on its title. Some information about this course is showed then: the course category, a summary, the due start date, the number of topics, and so on. The user can also see more detailed information about the course topics or the course content (see the use case “See the course content”).

Besides, some actions are available. The user could go to the course or unenrol from the course.

Deliverable 5.1.2


3.2.3 Enrol the user in a course of the e-‐Learning platform

Brief description

A member of the Virtual Community of Practice wants to enrol himself in a course of the e-‐Learning platform without leaving the VCP.

Preconditions



Flow of events

1. The user gets the list of courses in the e-‐Learning platform and finds a course in which he/she is interested on but in which s/he is not enrolled yet (see use case above “Get the list of courses in the e-‐Learning platform”).

2. As the user wants to enrol in the “Dementia” course, s/he fills out the application form to request being enrolled in the course. Then, the user clicks on the “Request course” button to send the request.

Deliverable 5.1.2


3. Once the request has been sent, a message is displayed saying that the request to enrol in the course has been sent successfully. The current status for the enrolment request is pending resolution. Besides, the user could cancel the request while it is still pending by clicking on the “Cancel request” button.

Deliverable 5.1.2


4. The administrator checks the course requests and sees there are new requests to enrol in the

“Dementia” course.

5. The administrator clicks on the “Dementia” course to check the pending enrolment requests for this course.

6. The administrator clicks on the “View” link to view the details about that request, such as the motivation and experience of the user that is making this request. Then, s/he clicks on the “Approve application” button to approve the enrolment request.

Deliverable 5.1.2


7. The user gets an email informing him/her that the request for the course has been accepted.

8. Finally, if the user goes back again to the course, a “You are already enrolled in the course!” message is displayed. The user can go to the course or unenrol from it.

3.2.4 Unenrol the user from a course of the e-‐Learning platform

Brief description

A member of the Virtual Community of Practice, who is enrolled in a course of the e-‐Learning platform, wants to unenrol himself/herself from that course without leaving the VCP.

Preconditions



The user is enrolled in the course he wants to unenrol from.

Flow of events

Deliverable 5.1.2


1. The user gets the list of courses in the e-‐Learning platform in which s/he is already enrolled and searches for the course s/he wants to unenrol from. Because s/he is no longer interested in the “Dementia” course s/he clicks on that course.

2. Then, the user clicks on the “Unenrol” button to unenrol himself from the course. A confirmation dialog is displayed. The user confirms that by clicking on the “Accept” button.

3. Once the user has been unenrolled from the course a “Enrol back in the course!” message is displayed instead. If the user wanted to enrol again in the course s/he should apply again by sending a new request.

Deliverable 5.1.2


3.2.5 Cancel request to enrol the user in a course of the e-‐Learning platform

Brief description

A member of the Virtual Community of Practice, who has previously requested to be enrolled in a course of the e-‐Learning platform, wants to cancel the request without leaving the VCP.

Preconditions



The user has requested to be enrolled in the course and his/her request has not been answered yet.

Flow of events

1. The user gets the list of courses in the e-‐Learning platform and searches for the course for which he/she wants to cancel the enrolment request (see the use case “ Get the list of courses in the e-‐Learning platform”). Since he/she wants to cancel the request for the “Dementia” course he/she clicks on that course.

Deliverable 5.1.2


2. In addition to the course information (course category, summary, start date, number of topics in

the course, and so on), there is a “Cancel request” button. The user clicks on that button to request his/her enrolment application in the course to be cancelled. Next, a confirmation dialog is displayed. The user confirms the request by clicking on the “Accept” button.

Deliverable 5.1.2


3. Once the request has been cancelled, a success message saying “Your request to enrol in the course was cancelled successfully” is showed. Later on, the user might try to enrol again in the course by filling out a new course request.

3.2.6 View the topics and content of a course of the e-‐Learning platform

Brief description

A member of the Virtual Community of Practice wants to view the topics and content of a course of the e-‐Learning platform without leaving the VCP.

Preconditions



The user is enrolled in the course (in case he wants to access not just to the list of contents but to the content itself).

Flow of events

Deliverable 5.1.2


1. The user gets the list of courses in the e-‐Learning platform or the list of courses in which s/he is enrolled and searches for the course whose topics and content wants to view. The user wants to get that information from the “Dementia” course, so s/he clicks on that course.

2. The user clicks on the “Course Topics” link in order to get a list of the different topics the course is about. For each course topic, its title and description is provided. Then, if the user clicks on the “Back” link, s/he is returned to the course page.

Deliverable 5.1.2


3. The user clicks on the “Course Contents” link in order to get a list of the available resources for every topic of the course. If the user is already enrolled in the course, s/he can access these resources by clicking on its links. Otherwise, the links to the resources will be disabled. In the same way, if the user clicks on the “Back” link, s/he is returned back to the course page.

4. Finally, the user clicks on the link of one of these resources to access it. For instance, the user clicks on the “Collaborative document about Dementia”, a resource of type Google Doc that is embedding its content into the Virtual Community of Practice Platform. This way, the user can edit

Deliverable 5.1.2


this shared document, which is available in the e-‐Learning platform’s course, without leaving the Virtual Community of Practice to log in the e-‐Learning platform.

3.2.7 Accessing a course of the e-‐Learning platform

Brief description

A member of the Virtual Community of Practice wants to go to a course of the e-‐Learning platform without leaving the VCP. Thus, s/he can manage that course in the same way as if s/he had logged in the e-‐Learning platform. However, the content is embedded in the VCP.

Preconditions



The user is enrolled in the course.

Deliverable 5.1.2


Flow of events

1. The user gets the list of courses in the e-‐Learning platform in which s/he is enrolled (see the use case: “Get the list of courses in the e-‐Learning platform in which the user is enrolled”) and searches for the course s/he wants to go to. The user wants to access the “Dementia” course, so s/he clicks on that course.

2. Then, s/he clicks on the “Go to the course button”. Since the course is embedded in the Virtual Community of Practice Platform, the user can view and manage it in the same way as is s/he had logged in the e-‐Learning platform and had accessed that course. The log in process in the e-‐Learning platform is made automatically for him/her.

Deliverable 5.1.2


3. There is also a “My Courses” menu on the right side of the site. This menu contains those courses in which the user is enrolled. If the user clicks on one of these entries, the user goes to that course. For instance, if the user clicked on the “Dementia” entry, it would go to the “Dementia” course too.

4 CONCLUSIONS This report has described the improvements made to the first release of the VCP Platform prototype reported in D5.1.1. This new version of the platform provides support for non-‐formal/informal competence recognition, and has also been integrated with the e-‐Learning Platform developed in T4.1. This second version of the VCP Platform will be populated with content provided by partners participating in task T5.2. This way, the platform will become the “seed” for nurturing Communities of Practice in the HHCP domain. The initial participants in those communities are expected to come from the face to face parts of the CARESS national pilots.

Deliverable 5.1.2


5 REFERENCES

[1] Wenger, E., McDermott, R. A., & Snyder, W. (2002). Cultivating communities of practice: A guide to managing knowledge. Harvard Business Press.

[2] CARESS project. “D3.6: VCP – environment conceptual design”. Project deliverable 3.1. April 2017.

[3] CARESS project. “D5.1.1: Virtual Communities of Practice (VCP) Platform – version 1”. May 2017.

[4] CARESS project. “D6.2: Evaluation and Monitoring Plan”. June 2017.

Documents

ERASMUS’PLUS’2015’ SECTORSKILLS’ALLIANCES’ · 2017-10-26 · Deliverable’5.1.2’ ’ 562634=EPP=1=2015=IT=EPPKA2=SSA’ ’’CARESS’Project’ ’3’of’45’ ’