Date: Thu, 28 Mar 2024 23:17:59 +0000 (UTC) Message-ID: <1349495919.85.1711667879899@debian.example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_84_604067629.1711667879898" ------=_Part_84_604067629.1711667879898 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page sets out to explain how HEIs that hold an Erasmus Charte= r for Higher Education (ECHE) can join the EWP network. Organisational unit= s of a given HEI (faculties, departments) or consortia are not allowed to c= onnect to the network separately.
If you are using software from a thir= d party provider, you will join EWP via your provider. Your provider will n= eed to upload information on the registration portal where the institution = (the so-called EWP-administrator= ) will need to confirm they are supported by this provider for using EW= P:
Once the steps above are completed, higher education institutions = can start exchanging data via EWP in their productive environment. They nee= d to use the functionalities provided by their provider who is responsible = for accurate training and support for using EWP-related functionalities.&nb= sp;
As part of their obligations, software providers agree not to add = additional APIs to their production manifest file before they have released= and tested these new APIs in the development environment.
One should keep in mind that things can go wrong. When institution= s violate the use of the EWP network there should be an exit strategy. Inst= itutions can report implementation issues of any particular node via the = span>ESCI Service Desk. The EWP management will try to settle disputes and has the authori= ty to exclude any institution from the production registry if it is in viol= ation of the terms of usage. The institution will need to prove its ability= and trustworthiness again in the development environment.