erasmus-without-paper / ewp-specs-mobility-flowcharts

"EWP Mobility Process Explained" document.
MIT License
3 stars 0 forks source link

Should the final ToR contain only courses passed during the mobility? #4

Closed wrygiel closed 8 years ago

wrygiel commented 8 years ago

@erasmus-without-paper/norway @erasmus-without-paper/sweden @janinamincer-daszkiewicz

  1. Should the final ToR (the one exchanged after the mobility ends) contain only these courses which were passed during the mobility?
  2. Or, should it contain all courses ever studied by the student in the receiving HEI?

I guess that the safest option would be to follow the current business process. So, the question is - how it is done currently (on paper)?

georgschermann commented 8 years ago

Differs from HEI to HEi. Most common practice here is to include all courses referring to the LA regardless of passed or not. Sometimes even not passed courses lead to a positive grade from the sending HEI. Some have requirements of minimal ECTS attended, with sometimes financial consequences.

vickalaser commented 8 years ago

The ECTS guideline is for all courses studies to be recorded on the LA and to appear on the TOR of the Host. These should then all be transferred to the TOR of the Home.

wrygiel commented 8 years ago

I'm designing input parameters for the Transcript of Records API just now.

janinamincer-daszkiewicz commented 8 years ago

I would rather assume that host institution will not care much about LA and will issue transcript with courses taken - some of them will report only passed courses, some will report all taken courses. It is probably quite common that host institution signs LA but them forgets about it.

wrygiel commented 8 years ago

My current (draft) version of the ToRs API takes mobility_id parameters (as opposed to student IDs). If we decide that this API should always return full ToRs (not just parts of them), then I think we should use student IDs instead.

wrygiel commented 8 years ago

We talked about it briefly in Warsaw. We have concluded that it is okay for ToRs API to be dependent on Mobilities API, and take mobility_id parameters. ToRs from our use cases should always be related to mobility.