You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »


9.00-9.10

Round of presentations of the Review’s   attendees

9.10-9.30

General introduction to:

  • Project objectives
  • Overview of the project objectives for the reporting period in question 

9.30-9.45

Q&A

no comments

9.45-10.30

Requirements   and architecture design (WP2)

what are used approaches for identifying competence needs? how are competences evaluated, is ESCO used in the background? Advice: make it more visible in the documents

what were the concrete activities that you came up with this framework for the services, stakeholders contacted? coherence of the process : have stakeholder needs been collected, what has been the activities, what they have said, their feedback? And how it's been used? Which criteria were used to select these services? How is stakeholder involvement and feedback documented? Advice: show the track record of the process, the criteria, stakeholder needs collected, plans validated by references groups, what tehy have added new and how thery tooks the initial sketches, and evidenced. Description in the deliverable, user scenarios, how and what kind of feedback from reference group, how was the design changed based on it, new ideas from the defence groups. Description of the process in more detail so it can be used e.g., in Italy in a similar process.

APIs? use of various data, lot of work. Where in this framework is the work that you do in the pilots? → not the entity of the framework within this project, framework is a vision?

What does the right to study entail? National context details, important to highlight them, make visible the different layers.

Two different concepts vision of the ecosystem, another element is the framework that every country could use, need to provide very clear indicators for it. Used as interchangaeable, but they are not, need to separate and specify. Crucial to describe the cooperation, use of ESCO and Europass and linkage to them.

Requirements description, what is the process of deciding which requirements are dropped and which are advanced? Is there a way to track this, somewhere described?

Learning analytics:

Other target groups than teachers and students, when have they been involved, what are the plans to involve them?

Paper reporting at EU?→ provide details of the conceptual review paper and the interview study, what interview question where used, documentation.

Designing the visualization and getting feedback from the end-users on the prototype > a little bit late, should have been started already. If presented with detail this could be stateof-the-art , need to have more detail and test with the end-users use of the prototype.

Relying on the deliverable was not enough to understand, needed to look into e-duuni, but there is a need to take key elements out of there to present the full ecosystem and teh achitecture framework. Not just explain the end-results, but also the way you got there.




10.30-10:45

Q&A

10.45-11.15

Prototype   development  (WP3)

How user select the education competences→ where is mapped to? Identified vs unidentified, mapping free text to study profile?

new, unidentified user, how to support, provide value, and "catch" such user?

What is the jobs section?

Concern: have the mock-up, why do you need the html, if the data is also mock-up?

WP3 is late, this is a concern, what is the plan for going forward? Updating the project roadmap. With the delay, what is the plan B?

What is the Beta version? Now planned to be ready in M18, if not, how is it going to affect the other activities?


11:15-11.30

Q&A

11.30-11.45

Coffee Break

11:45-12.15

Deployment   and evaluation (WP4)

12.15-12.30

Q&A

12.30-13.00

Dissemination,   communication, eploitation (WP5)

13.00-13.15

Q&A

13:15-14.00

Lunch   Break

14.00-14.30

Project   management

14.30-14.45

Q&A

14.45-15.15

Deliverables

15.15-15.30

Q&A

15.30-15.45

Coffee   Break

15.45-16.15

Finance,   Use of resources

16.15-16.30

Q&A

 

16.20-16.50

Private   meeting between the Reviewers and the Project Officer – Outcome of the review

 

16.50-17.00

Feedback   and recommendations from the Project Officer and the Reviewers

  • No labels