• Paikalla: Eva Neffling (EDUFI), Antti Laitinen (CSC), Annica Moore (EDUFI), Mika Launikari (Everis/Europass), Janne (Reaktor)


  • Short introductions
    • Mika's role in Europass is to ensure the guidance and user-driven experience. Mainly he is busy with the content production.
    • The big picture of Europass is looking chaotic. The launching is in Spring 2020.


  • Europass Case Study - background
    • Has come from the commission without a proper guidance - the main point: what's useful for all parties? 
    • The approach and the budgets are different in CompLeap and Europass but for example the goals are similar.
    • A lot of architecture work has been done in CompLeap which could be useful for the chaotic development phase of Europass.
    • An algorithm is something that can "live" after the CompLeap project is over but we should also keep in mind the future after the project is over from other perspectives too.
    • How does the guidance is shown in Case Study?
    • What does the guidance mean in this case? Mika:- is the service user-friendly - does it support lifelong learning - learning, career development, jobhunt
    • Europass: A user study in September - individual end-user can use the prototype
    • Is the Europass proto available? - At first it will be availbe in a closed group.
    • In the long run Europass has a will to build similar features than in CompLeap's interests - Mika has made a research about this for William - some kind of version released in the spring 2020
    • What kind of data the suggestion system is using in Europass?
      • user profile
      • Ploteus (learning opportunities and qualifications) - Europass Advisory group: the criteria of how education programmes and education opportunities can be searched is still "in the air"; the priority is in the higher education - How the information is got from the member countries is a big question?
      • CompLeap has couple of potential international deployment partners that could offer an example what kind of national data is available 
      • Funding has been given previously to member countries concerning Ploteus - which wasn't really thought through - it is not a sustainable solution for transferring education information
      • EURES collaboration (job opportunities)


  • CompLeap prototype: focus on algorithm and education opportunities
    • In development: a section where ESCO competence will be visible
    • PoC is part of a competence profile in a bigger context  - in PoC a bigger vision is tested in a smaller scale
    • Are the results plausible? How satisfied are we?
      • HTML prototype is similar to Europass prototype
    • At the moment too much is tried in Europass in relation to schedule
    • Competence vs. skills - according to commission "competence" shouldn't be used
      • Strong authentication: Does the information come directly or is it transferred? A difficult question - people with a long education history make it scrappy  - the main thought is the automatism - not like in LinkedIn where a user can add anything they want
    • Algorithm: What kind of problems have been solved?
      • It has been done in natural language - the education related descriptions - is written for a human user 
      • By machine learning semantic meanings are sought
        • combined with interests a service offers suggestions
      • Challenges:
        • The approach requires that the text needs to be similar: eRequirements - the descriptions of the education is written in the "official language" 
        • the used data needs to be similar in quality
      • Emphasis: what information is more meaningful than other?
        • Prior education + interests - only limited amount of data is used
        • Work experience and the education history is empasized so that the most recent ones are prioritised


  • Next steps
    • Europass Architecture
      • Meeting in August - September
    • Valentina Azzarella (Everis)
    • William is on a Holiday until 20th August
    • Mika will contact Eva



  • No labels