Hi Jiri
This would be ok with me.
When Nexis introduced their refreshed user interface in the UK we had some discussion on our eResources listserv and I raised it with the UKFAM.
Nexis replied:
“If customers do not wish to authenticate directly this is OK. We are in the final stages of setting up OpenAthens & UK Federation (Shibboleth) against the refreshed user interface. So long as a Permanent identifier (rather than Transient)
is sent we have relaxed the validation rules against Forename, Surname, and Email Address to allow accounts to be created without these items being present.”
This did cause us a few issues, as we had some problems a few months ago when I think they made some further changes and (perhaps) forgot we had requested this (because
some users were being asked for name and e-mail again) so the more we can standardise this the better.
All the best
Caroline
Caroline Checkley
Digital Systems and Services Librarian
Library Services
University of Essex
E checkc@essex.ac.uk
► http://library.essex.ac.uk/
From: FIM4L <fim4l-bounces@lists.daasi.de>
On Behalf Of Jiri Pavlik
Sent: 11 March 2021 08:05
To: fim4l@lists.daasi.de
Subject: [Fim4l] LexisNexis Advance
|
CAUTION: This email was sent from outside the University of Essex. Please do not click any links or open any attachments unless
you recognise and trust the sender. If you are unsure whether the content of the email is safe or have any other queries, please contact the IT Helpdesk. |
Deal all,
in eduGAIN LexisNexis Advance SP request optionally eduPersonScopedAffiliation and eduPersonTargetedID attributes. [1] In Austrian
eduID.at it requests these two attributes as required. [2] In French RENATER it requires eduPersonScopedAffiliation, eduPersonTargetedID, givenName, sn, mail attributes and supports Code of Conduct and Sirtfy entity categories. [3]
I am wondering whether everyone could be fine with following set of attributes along with CoCo and Sirtfy entity categories support:
eduPersonScopedAffiliation (required)
eduPersonTargetedID (optional)
givenName (optional)
sn (optional)
mail (optional)
Universities/libraries may choose to release just eduPersonScopedAffiliation and be FIM4L privacy stars. It will correspond to the upcoming REFEDS Anonymous Authorisation entity category. [4]
Universities/libraries may also choose to release eduPersonScopedAffiliation and eduPersonTargetedID for enabling personalisation capabilities. It will correspond to the upcoming REFEDS Pseudonymous Authorisation entity category. [5]
And finally universities/libraries may also choose to release eduPersonScopedAffiliation, eduPersonTargetedID and let users decide about releasing name and e-mail address. [6]
Do you like this kind of approach?
Take care
Jiri Pavlik,
techlib.cz