...
Below is a detailed overview of the different steps that need to be taken during this procedure.
Step-by-step
| Expand | ||
|---|---|---|
| ||
As a first step it is important to understand the basics (different scenario's for joining Erasmus Without Paper, the mobility process cut into pieces) of the Erasmus Without Paper infrastructure and apply it to the management of mobility processes at your own institution. |
| Expand | ||
|---|---|---|
| ||
The implementation of Erasmus Without Paper in your inhouse in-house software needs to be done by your IT team. We encourage you to involve them in the process right from the beginning. They will be responsible for developing the APIs that connect your own system to the system of your partner via the Erasmus Without Paper network using the communication protocols. |
...
| Expand | ||
|---|---|---|
| ||
Although your IT team will be responsible for connecting your system to Erasmus Without Paper, you will need to rethink existing business processes because you will need functionality to send data to your partner institutions or handle data that you receive from your partner. We strongly advise that the IRO as a business process owner is directly involved in the rethinking of these processes. |
Entry procedure
The so-called EWP-administrator from the institution looking to join the Erasmus Without Paper network, will need to login to the registration portal where she/he will need to add a signed Collaboration Agreement and add the url to the so-called manifest file.
...
| Expand | ||
|---|---|---|
| ||
The EWP admin can now upload the link to its manifest file. Only APIs that were tested during step 1 can be included in the manifest file. When the provider would like to declare endpoints for new processes, they need to undergo the step 1 testing with the reference implementation. |
Start exchanging via Erasmus Without Paper
Upon completion of the 4 steps above, the higher education institution is added to the Erasmus Without Paper registry (this can take some time) and becomes part of the Erasmus Without Paper network. The higher education institution can start exchanging data via Erasmus Without Paper in their production environment. They need to use the functionalities provided by their in-house system.
As part of their obligations, software providers agree not to add additional APIs to their production manifest file before they have released these new APIs in the development environment and tested them with the reference implementation.
Revocation
One should keep in mind that things can go wrong. When institutions violate the use of the Erasmus Without Paper network, there should be an exit strategy. Institutions can report incidents and complain about the quality of APIs of any particular institution, the unavailability of a server, partners that are not trustworthy, etc via the ESCI Service Desk. The EWP Governance structure will try to settle disputes and has the authority to exclude any institution from the production registry if needed. The institution will need to prove its ability and trustworthiness again in the development environment. In cases of extreme violation the EWP governance structure has the competence to temporally exclude an institution from the Erasmus Without Paper production network.