General questions
Expand | ||
---|---|---|
| ||
EWP stands for Erasmus without Paper, which is a project and now a Network funded through Erasmus+ KA3 from 1/11/ 2015 till 30/10/2017 and again from 1/1/2018 till 31/12/19. Its chief goal is to digitalise the administrative framework that underpins student mobility in Europe, enabling electronic data exchange and interoperability among diverse information systems. In March 2019 the European Commission announced that the usage of EWP will be made mandatory from 2021 as part of the next Multi-annual financial framework (MFF) i.e. the next Erasmus programme. This was confirmed and elaborated in the Erasmus goes digital webinar on 5/3/2020. EWP consists of two chief components: a network that interconnects a multitude of student information systems (whether individual universities or third-party providers which represent multiple institutions) through the use of APIs and a Dashboard that provides a web solution for exchanging student data electronically for HEIs lacking the required SIS software. The present document focuses exclusively on the EWP network and the connection to it; the compliance and use of the dashboard is the object of a different set of documents. |
...
Expand | ||
---|---|---|
| ||
In March 2019 the European Commission announced that the EWP standards will be mandatory from the beginning of the new Erasmus Programme in January 2021. The timetable they put forward was: In practice there are 3 ways to do this: A combination is possible, but you cannot combine tools for the same API service. In practice, this means that HEIs can gradually introduce the changes, even though the EWP Network already has operational APIs for all of the processes in student exchanges as we speak. For a detailed description of the EWP APIs click here. Our third-party provider EWP partners (Mobility Online (AT), MoveON (UK), USOS (PL), Cineca (IT), Sigma (ES), FS (No)), have committed to implement all APIs in their business development plan, but the exact timetable is, of course, their own responsibility. You could also start with one solution for a particular API service and later on change to another one, as long as you don't use two solutions for the same service. |
...