...
HEIs get agency and tools to manage their connection to the Network. This goal is achieved by giving institutions the way to sign in to the Registration Portal with the credentials passed from their home authorisation system and the right to approve their manifests. |
In the Registration Portal all stakeholders – HEIs and mobility software providers – manage all network parameters of their connectivity by themselves, anytime. Registry administrators and EWP network authorities also can handle the needed activities via the web portal. | ||||
All important documents, such as the signed EWP Collaboration Agreement, are gathered in one place which is easily accessible to all stakeholders. |
In line with the carefully crafted verification rules, the portal supports security and ownership by verifying the identifiers (such as SCHAC code) transported in the set of attributes from MyAcademicId against identifiers obtained from other sources (ECHE List API, HEI List API, manifest files). |
...
Actions performed in the Registration Portal
In this section, we shortly explain what steps actions providers and HEI representatives should perform to properly register their manifests in the EWP network. The only way to place the manifest on the Internet is for the provider to enter it into the Registration portal, verify the correctness of the manifest (including the APIs it contains) and have the manifest confirmed by the HEI for which it is intended.
3rd-party provider |
|
In-house provider (represented by the EWP Administrator) |
|
...
Important functionalities of the Registration Portal
...