Hi,

yes, the guidelines document is aiming to cover both the single- and the multiple-contract cases. 

All the best

           Jiri



On Wed, 20 Mar 2019 at 21:22, Peter Schober <peter.schober@univie.ac.at> wrote:
* Jiri Pavlik <jiri.pavlik@mzk.cz> [2019-03-20 22:14]:
> I see. common-lib-terms in entitlement attribute or usage of
> eduPerson(Scoped)Affiliation are fine for authorisation handling
> based on single contract with publisher

Exactly, and there are (technical) advantages in using one over the
other, resulting in less need for 1:1 coordination between publisher
and institution and therefore more "It Just Works".

> but not sufficient for multiple contracts. The multiple contracts
> are pretty common in Czech Republic.

I have essentialy zero practical exposure to your scenario (as the
opposite seems to be the case in Austria) so I'm happy to learn.

So I guess a guidelines document would have to differentiate between
the single- and the multiple-contact cases? That adds complexity but
this seems unavoidable if both use-cases are common and have to be
dealt with.

-peter
_______________________________________________
Fim4l mailing list
Fim4l@lists.daasi.de
http://lists.daasi.de/listinfo/fim4l