Open wrygiel opened 8 years ago
as of our customers this differs from HEI to HEI, some exchange them without the student even seeing the ToR
some exchange them without the student even seeing the ToR
The important question is: Are all HEIs aiming to achieve the same effect?
Or perhaps it's exactly the opposite? That is: some of them claim that the law doesn't allow them to exchange ToRs themselves, and it is the student who has to do it?
from out experience, most of the HEIs will aim to do it automatically, maybe for some there are legal constraints
I think we should assume there will be all variations and therfore allow for it.
To sum up:
Is this correct?
I think we should start with designing just the required part for now.
We shouldn't be concerned about the students' involvement, as the EWP Network provides solely an interchange for institutions. The EMREX will benefit from it if it plugs itself into the system and then also provides the data to students but it would act as a 3rd party tool.
Therefore, EWP needs to cater for the following two use-cases
The responsibility of making it available to the student lays with the institutions.
I agree that a successful nomination should be the "flag" to allow for ToRs to be sent. The moment when the ToR is being triggered by either side shouldn't be defined though.
The sending institution sends back a ToR with converted grades to the receiving institution
Do you mean "mobility recognition data"? By this I mean information on which elements in the LA has been recognized and how.
If so, then this is a completely different topic. The topic raised here is about sending ToRs for admission - such ToRs would include data on courses been studied before the mobility.
We are not required to design solutions for exchanging ToRs before the mobility begins. But it might be in our interest do so. It can make more HEIs interested in EWP.
Currently, ToRs APIs is to be implemented by the Receiving HEI only. If we really want to pursue this topic then we will probably need to allow the ToRs API to be implemented by the Sending HEI, and add a new parameter indicating if we want a complete ToR of the student related to mobility_id
or just the records related to particular mobility.
To be discussed on one of the future meetings.
(it's not among our use cases, we can use EMREX for that)
The comment above was a quick "note to self" posted directly during the meeting. Followup: We have discussed this and have confirmed that this is really out-of-scope of EWP. The receiving institution should use EMREX for this purpose. We MAY come back to this topic in the future, but we will close this issue for now.
In the current version of the document I have claimed the following:
However, I am not 100% sure if we indeed MAY require this of students. Perhaps students should use the EMREX flow instead (submit only these courses they want to submit).
@erasmus-without-paper/norway @janinamincer-daszkiewicz