Blended Mobility

[Belenchusky]

We are developing the new IIAS template right now and we have a problem with the blended field. This field is at the agreement level,neverthelesin the GET API the same filed operate for each Student Mobility for Studies.

That's a contradiction, isn´t it?

[kamil-olszewski-uw]

During the adaptation of IIAs API to the rules of the new Erasmus+ edition, a design decision was made (with the knowledge and consent of the EUF) that the "Blended" field would be at the cooperation conditions level, which would allow for more clarity and less surprises.

[Belenchusky]

I agree with you, but who is in charge of bringing the decision made in the API to the template? I just checked it online and the API mismatch still exists.

[lioliosn]

There is no contradiction. The blended option is not at the agreement level as it refers only to students and not to staff mobilities. Therefore, the API connected more effectively this condition to students' mobilities. It is the template's business logic that it is translated to API specs.

[Belenchusky]

@lioliosn I see your point of view but that implies that this condition affects all student mobilities that you have in the same agreement and that is not always the case.

Let me show a real agreement signed through EWP between our university and P BEJA 01. As you can see, I had to change the template to be able to represent the information that is obtained from the GET API.

[lioliosn]

@Belenchusky if you have a look at the API specs, it fits exactly your use case. You have blended mobiliyty option for every mobility flow per subject area code. I understand that your problem is the template, but the API has solved this for you.

[Belenchusky]

@lioliosn Yes, the problem is the official IIA template. As you can see I had to modify it on my own.