-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moving nomination status to Incoming Mobilities API #32
Comments
This proposal resolves indeed our issues with the status-updates. |
Marta, I see no objections. Let's finalise the change. |
Changes submitted: |
@BavoNootaert @MartaJuzepczuk @janinamincer-daszkiewicz Sorry I hadn't had the time to look into this earlier. |
Thank you for your notice. We would prefer not to extend the NominationStatus, to keep it clear who is the master of the MobilityStatus. However, you are right that there should be a way to inform sending HEI about shortening or extending the stay, or about the situation when the students did not show up. There is one unreleased commit, which we are going to release until tomorrow. In this commit we add a new field with a comment to the Incoming Mobilities response. We planned to name it After internal discussion, we came up with a solution to change the name of For example: Situation 1: Student did not show up.
Situation 2: Student leaves earlier. |
@erasmus-without-paper/all-members
We plan to move accepting nominations from Outgoing Mobilities update endpoint to Incoming Mobilities get + CNR.
As proposed here, we will introduce second mobility status, let's call it
nomination status
, owned by the receiving HEI and sent through Incoming Mobilities API.In details:
nomination-verified
andrejected
.status
, with three possible values:pending
(no decision made),verified
,rejected
.nomination status
(status from Incoming Mobilities API) and the sending institution is the master of mobility status (status from Outgoing Mobilities API).get
.Does it fit you? Do you think we should make some changes in this proposal? We plan to release new versions of Incoming and Outgoing Mobilities APIs in a few weeks.
Discussion about removing update endpoint was in #25 and #31.
The text was updated successfully, but these errors were encountered: