Steps to join

13th October 2016

The EMREX network is eager to add new participants. Anyone interested can contact the project to get help. Here is also a short description on what we see as the first steps.

Note that EMREX is open source and the components are offered free of charge.

Steps on how to join

1. Decide on the process and purpose of using EMREX. What process is it supporting? Who will the users be?

EMREX can be used as a building block for many different processes.

  • recognition of external studies during an exchange period (e.g. Erasmus, Nordplus etc)
  • internal mobility within a country
  • verifying prior learning
  • to come: verification of credentials, e.g. for degree mobility or employment needs

The project is willing to discuss with you your case and how EMREX can be used to support your needs.

2. Read the technical guide and have a look at the source code in GitHub and the elmo-standard.

The technical guide and case study will give a good overview of how EMREX works. The source code and especially the elmo-standard in GitHub will allow technical experts to estimate the workload needed to join the EMREX network.

The technical parts can be re-used in your development. Also the stand-alone solutions can be used to quickly set-up a test component.

Note that the key issues usually are

  • how will be students be authenticated?
  • how and from where can we get the achievement records?

3. If needed, ask for a technical telco or workshop to answer any open questions or to set up a proof-of-concept

If the infrastructure is in place, it only takes a couple of weeks to set up an EMREX test system. The project is happy to help and arrange a technical telco, or even a workshop around EMREX to work out a proof of concept.

4. Apply for registration to the EMREX test network (to the EMREG register). Each NCP needs to be registered

Joining the test network is free of charge. The test-NCP needs to be registered to the test network, i.e. the IP address and public key published. In the test network other partners NCPs/SMPs can be utilized to test against your own development.

5. Set up your own test SMP and/or NCP. Including also authentication of the users and connection to the results service

Test together with the partners in the EMREX network

6. Go to production and sign up for the EMREX network

After a successful testing phase the solution is ready to join the EMREX network. This can be done either with only the SMP or NCP part, or with both together. It is possible to first try e.g. the receiving end and only later provide own data. This could be the case if e.g. access to a common results service is difficult.

The EMREX network is built on trust. Each user and organization needs to trust that the achievement records received are for that student, untampered with and from a valid source. The EMREX network ensures that the results are transferred in a secure and reliable way. In addition there is a need to ensure that the source can be trusted.

The National Contact Points (NCP) are the ones responsible for retrieving the student achievement data to be sent. Therefore it is essential that the other party can trust the NCP and that the NCP e.g. only sends data from recognised HEIs.

The following principles have been agreed to ensure only valid NCPs can join the EMREX network.

  1. The EMREX user group verifies and approves new NCPs, before they can be registered in the EMREX network, i..e added to the EMREG. Before the EMREX user group is formed, the decision is taken by the EMREX Project Group.
  2. The above groups also have the authority to revoke the registration at any time, if the conditions are no longer met.
  3. To be approved as a NCP at least one of the following conditions must be met:
    1. The organization setting up the NCP has a valid Erasmus PIC code and is thus recognised as a valid Higher Education Institution, or
    2. At least one of the existing members of the EMREX network has verified that the Applicant is a valid organization, or
    3. The Applicant can provide other documentation to validate its trustworthiness as a NCP