The EWP Stats Portal contains statistics coming from providers about the number of IIAs and LAs shared and approved via the EWP network. The data displayed comes from various sources: ECHE List, Registry Catalogue file, and other trustful sources.
The EWP Stats Portal has built-in functionality for searching and filtering data. It enables the exploration, analysis, and visualisation of data on activity, errors, and statistics on data exchange for the nodes in the network. Data needed for statistics are fetched from the stats endpoints implemented by the nodes in the network. Communication errors are reported by the nodes to the monitoring API implemented by the Stats portal itself.
This section explains how the portal operates, how to search for information on nodes in the network, how to interpret displayed charts, how to search and filter error reports, how to prepare data on other trustful data sources.
This section explains how the portal operates, how to search for information on nodes in the network, how to interpret displayed charts, how to search and filter error reports, how to prepare data on other trustful data sources.
Read about the Stats portal:
Gathering statistical data in the EWP network (by DG EAC):
New service to identify which of your partners use Erasmus Without Paper.
EWP+ Stats portal: identify which of your partners use EWP+.
Stats endpoints
The following business level statistics were identified as proper indicators of the state of the digitalization in the area of inter-institutional agreements and learning agreements.
Inter-institutional Agreements (discussion in GitHub) | |
---|---|
Number of IIAs created in the local system which can be fetched by the partner HEI. | Total |
Number of IIAs created in the local system which have been approved by the partner HEI but the matching copies of the partner have not been approved by the local HEI. | Approved only by partner |
Number of IIAs created in the local system which have not been approved by the partner HEI but the matching copies of the partner have been approved by the local HEI. | Approved only locally |
Number of IIAs created in the local system which have been approved by the partner HEI and the matching copies of the partner have been approved by the local HEI. | Approved by both sides |
Learning Agreements for outgoing (sending HEI) (discussion in GitHub). All statistics grouped and ordered by the academic year. | |
---|---|
Number of LAs. | Total |
(only before the mobility) Number of LAs with one version approved by the receiving HEI which has not been followed by any other version. | Not modified after approval |
(before and during the mobility) Number of LAs with at least one version approved by the receiving HEI and with some versions after the approved one. | Modified after approval |
Number of LAs with the latest version approved by the receiving HEI. | Later version approved |
Number of LAs with the latest version rejected by the receiving HEI. | Latest version rejected |
Number of LAs with the latest version awaiting receiving HEI’s approval. | Latest version awaiting |
Learning Agreements for incoming (receiving HEI) (discussion in GitHub). All statistics grouped and ordered by the academic year. | |
---|---|
Number of LAs. | Total |
Number of LAs with at least one version approved by the receiving HEI. | Some version approved |
Number of LAs with the latest version approved by the receiving HEI. | Later version approved |
Number of LAs with the latest version rejected by the receiving HEI. | Latest version rejected |
Number of LAs with the latest version awaiting receiving HEI’s approval. | Latest version awaiting |
Formal specifications are available in GitHub:
More information can be found in the Architecture and Common Datatypes specification.
Additional requirements:
Only IIAs/LAs exchanged via the EWP network should be counted.
Cumulative numbers should be reported. The Stats portal will store all delivered data sets.
For LAs the smallest reported academic year should be 2021/2022. All earlier academic years, if present in data, will be skipped.
Server should respond as fast as possible. If online calculation of statistics can not be finished in an assumed time, it is better to calculate them offline.
Server MUST allow the Stats portal to access this endpoint. The Stats portal is identified by SCHAC code
stats.erasmuswithoutpaper.eu
.
More endpoints will be designed after new processes are officially deployed in the EWP network, like Nominations, Transcript of Records.
More endpoints will be designed after new processes are officially deployed in the EWP network, like Nominations, Transcript of Records.
Data sources
Data displayed in the Stats portal comes from various sources which are described in this section.
The ECHE List API is the basic trustful source of data on ECHE holders. The list is available at this address and delivers the following APIs. These APIs expose all institutions that currently hold the Erasmus Charter for Higher Education as published by the European Commission. All the data fields contained in the original list are made available to client applications. Additionally, some processed values are also provided to respond to more specific use cases.
Only ECHE holders are displayed in the PROD installation of the Stats portal. In DEV all data are shown because some providers use dummy SCHAC codes, not representing any ECHE HEI.
The EWP Registry catalogue file contains information gathered from all registered manifest files. There are two instances of the file.
The statistical data are obtained from the stats endpoints. The EWP Stats portal collects data from all nodes, but the PROD installation displays only data from ECHE holders.
The EWP Stats Portal can also display data coming from other trustful sources. For example, we currently upload data from the RAD-on system operated by the Polish Ministry of Education and Research. It contains the most authoritative data on Polish higher education and science institutions. Any such data coming from other countries can be easily uploaded to the Stats portal by a script that reads and processes data from a file in a given format.
Gathering statistical data
The EWP Stats portal collects data starting from January 1st, 2023. Statistics are gathered periodically, on agreed days. Nodes may calculate statistics on-line or off-line. If statistics are calculated off-line, they should be as fresh as possible on the day of request. Currently the agreed times of data collection are the following:
DEV network – daily at 4:00 CET.
PROD network – every 1st day of the month at 20:00 CET.
Statistics are gathered only from nodes implementing Discovery API 6.0.0 or higher and it takes approximately 20 minutes.
If an HEI changes provider, it should take its data to the new provider and make it available in the network. This means in particular that all data should be included in the statistics provided by the HEI from the new location. Stats endpoints for the HEI can be available in only one place in the network at a time. The EWP Stats portal stores information about the provider who delivered data on a particular day.
Quality of data
The accuracy of the displayed statistics is the sole responsibility of the parties providing the information.
Completeness of data
Not all providers are yet providing complete statistical data sets, which means that statistics are available only for some clients in some cases. This limits the way any analysis can rely on statistical data from all connected providers to draw a global picture of the current state of play.
Installations
There are two installations of the EWP Stats portal.
The Stats portal has its own manifest file
The SCHAC code of the Stats portal is stats.erasmuswithoutpaper.eu.
Nodes may limit access to their stats endpoints to this server.
Sample statistics
These are sample statistics on IIA and LAs for 01/09/2023.