In order to join the EWP Network institutions need to have an Erasmus Charter for Higher Education; accordingly organizational units of a given HEI (faculties, departments) are not allowed to connect to the network on their own. In order to join the EWP network you first of all you need to decide which category of user you are. You don't join or register for EWP personally, your institution does. The following only refers to the connection to the EWP Network, ie. HEIs wanting to connect their internal software or third-party providers who want to connect their clients. If you only want to use the EWP Dashboard (also known as the Erasmus Dashboard), there is another procedure to follow.
Joining in short
- The URL to the manifest file is added to the development registry (DEV):
As a first step of the technical admission, upon approval of the EWP Steering Committee, the institution will be added to the development registry. Therefore a manifest file and its corresponding URL will be needed. The manifest file contains information about the supported API’s APIs and hosts. The URL will be added to the development registry and as a first step the ECHO API needs to be developed.
- The applicant institution performs some automated self-tests;
- The applicant institution performs testing with three partner institutions.
Newcomers will need to demonstrate their technical ability to exchange real data in the development environment. Therefore they will need to develop at least one of the APIs (apart from ECHO) that facilitate real exchange of data between HEIs. Before an applicant institution can become part of the production registry, the institution needs to prove successful testing.
- The EWP technical team performs some ultimate technical testing before adding the institution to the production registry (PROD).
The final step of the technical admission consists of an ultimate series of tests by the EWP technical team. Each of the APIs supported by the applicant will undergo this testing.
For trusted software providers only this final step is needed.
We should keep in mind that things can go wrong. When institutions violate the use of EWP there should be an exit strategy. The Competence Centre will be the central point where institutions can report incidents and complain about the quality of APIs of any particular institution, the unavailability of a server, partners that are not trustworthtrustworthy. The Competence Centre will try to settle disputes and has the ability to decide to exclude a certain institution from the production registry. The institution will need to prove again its ability and trustworthiness in the development environment. In cases of extreme violation the Competence Centre has the competence to temporally exclude an institution from EWP.
The entry procedure for institutions who want to join EWP via their in-house or 3rd party software above is currently revised , aimed with the aim to automate the entry procedure via through a web application. We hope to release this new entry functionalities functionality in the course of 2021.