search

erasmus-without-paper / ewp-specs-api-omobilities

Specifications of EWP's Outgoing Mobilities API.
MIT License
1 stars 4 forks source link

Mobility's academic year #24

Closed wrygiel closed 6 years ago

wrygiel commented 7 years ago

In order to properly "verify" mobilities against IIA's conditions, we will need some kind of mapping between the mobility and the academic year. Let's call such academic year a "connected" one (we will probably need a better term before we introduce this).

Previously I was thinking that this mapping could be extrapolated from <planned-arrival-date> and <planned-departure-date> , but this doesn't seem to be the case. Some mobilities begin or end in different academic years than those with which they are "connected". So, it would seem that we need an extra element for that.

I'm not yet sure, if the type of this extra element should be AcademicYearId or <academic-term>?

Note, that we are also planning to make <planned-arrival-date> and <planned-departure-date> optional. So, this new element would be the only temporal property of newly created nominations.

wrygiel commented 6 years ago

This issue is no longer valid. We have already introduced the <receiving-academic-year-id> element.