The answer depends on what category of user you are. If you are an HEI without any dedicated mobility software, you can use the EWP/Erasmus Dashboard (for Online Learning Agreements and/or Interinstitutional Agreements) to connect to the EWP Network. If you use a third-party provider they will be connecting you to the EWP Network. But if you have your own internal Student Information System (SIS) mobility software, you will need to have ICT support to connect your software to the EWP Network and implement the APIs. In that case there are 2 main tasks that have to be done:
- the server of your HEI has to be connected to the EWP Network (giving the EWP APIs access to the data stored in the databases - this is implemented in the back end of your system) but
- your present software interface has to be adapted as well to give the user access to the new possibilities - this part has to be implemented in the front end of your system). Some would also call this distinction server-side and client-side implementation respectively.
Your technical solution may combine several types of implementation as a start (e.g using third party software for some services, your own system for others and the Dashboard for Online Learning agreements and/or the Interinstitutional Agreement Manager) but you always have to make sure that the same service (API) is implemented by only 1 solution. You can, therefore, implement APIs in a phased way.