As a first step the higher education institution needs to undergo a technical admission procedure: The EWP admin of the applicant higher education institution needs to login as a higher education institution in the registration portal staging environment, a copy of the production environment linked to the Erasmus Without Paper development network (please note that if you are not an EWP admin at your institution or your institution does not release this attribute for you (you can test this here), this step will fail, please contact the ESCI Service Desk); In this portal the higher education institution will need to upload a signed Collaboration Agreement determining the terms of use of the Erasmus Without Paper (development) network and setting the conditions to link the in-house software to the Erasmus Without Paper (development) network; Upon the countersigning of the Collaboration Agreement by the EWP+ Consortium, the EWP admin will be informed; The EWP admin will upload a link to the manifest file (this manifest file contains amongst other things information on which APIs the provider supports for the higher education institution in question) for its testing instance; The in-house provider performs some automated self-tests; The in-house provider contacts the ESCI Service Desk with a request for information or guidance (non-student issues) asking to test their APIs with the reference implementation; The EWP technical team will go through the testing scenarios for IIAs inter-institutional agreements and/or LAs learning agreements as described in GitHub.
|