- FIM4L - lists3.daasi.de

Invitation: FIM4L meeting @ Thu 4 Apr 2019 15:00 - 16:00 (CEST) (fim4l@lists.daasi.de)
by jos.westerbeke＠eur.nl 22 Mär '19

22 Mär '19

You have been invited to the following event. Title: FIM4L meeting Agenda:- Welcome- Discuss finalisation of FIM4L proto-charter (editing, how to publish)- FIM4L guidelines and recommendations - Use of FIM4L email list: Technical discussions included?and recent adoption of GEANT Data Protection Code of Conduct by RA21. When: Thu 4 Apr 2019 15:00 – 16:00 Central European Time - Amsterdam Joining info: meet.google.com/ppq-dqwn-zgo <https://meet.google.com/ppq-dqwn-zgo> Calendar: fim4l(a)lists.daasi.de Who: * jos.westerbeke(a)eur.nl- organiser * fim4l(a)lists.daasi.de Event details: https://www.google.com/calendar/event?action=VIEW&eid=NmhtdWowdm5hM2JodmMyY… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account fim4l(a)lists.daasi.de because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively, you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Fwd: RA21 Adopts GEANT Data Protection Code of Conduct
by Jiri Pavlik 21 Mär '19

21 Mär '19

FYI ---------- Forwarded message --------- From: Julia Wallace <julia(a)ra21.org> Date: Fri, Mar 15, 2019 at 10:05 AM Subject: RA21 Adopts GEANT Data Protection Code of Conduct Privacy Matters! The RA21 project is pleased to announce its endorsement of the GEANT Data Protection Code of Conduct. Earlier this year (2019), the RA21 Security & Privacy group endorsed the GEANT Data Protection Code of Conduct as guidance that RA21 should follow: data minimization, purpose limitation, data retention, and more. What does data minimization mean in an RA21 context, where users are trying to access scholarly information resources, particularly in an academic setting? It means that unless the Service Provider (such as a publisher or other content vendor) has a specific agreement with an Identity Provider (IdP - usually an individual’s institution) to receive additional data the IdP should only send anonymous and pseudonymous identifiers to the Service Provider. Specifically, the service provider should only ask for eduPersonEntitlement and, optionally, a pseudonymous pairwise user identifier (e.g., eduPersonTargetedID). In the case that the IdP sends more attributes than those one or two requested by the Service Provider, the Service Provider must not collect or store that data under any circumstance. The endorsement of the GEANT Data Protection Code of Conduct and the specifics around what attributes may be requested feeds directly into the upcoming NISO Recommended Practices for Improved Access to Institutional Information Resources, expected to go out for public comment in the next few weeks. Expect another announcement from us as soon as that comment period opens.

4 15

initial questions
by Peter Schober 21 Mär '19

21 Mär '19

Dear all, I've recently subscribed to this list due to Raoul dropped its short name (FIM4L) on another mailing list and from then finding a czech language presentations on the Internet with contained links to this mailing list. The "charter" document referenced by Jiří yesterday answers a few of my questions with regard to the background (and possibly funding) of this effort but raises others (E.g. Why is this not a REFEDS Working Group? How come the identity federation community at large has never heard of this and has not been given a chance to provide input but eduGAIN, GEANT and REFEDS are already listed as "parties involved in this effort"? etc.) Both the charter and especially the "FIM4L guidelines and recommendations" documents referenced in the mail yesterday are fraught with issues, IMHO, both substantial and structural/editorial. So how do you want to handle this? Should I wait like everyone else who hasn't been invited into this effort until you consider those documents ready for wider publication? Or do you want to gather more input now -- but then why limit that additional input to myself only because I've managed to even find this list and not the wider community? Best regards, -peter

5 7

Next FIM4L call
by Jiri Pavlik 17 Mär '19

17 Mär '19

Dear all, you can indicate your availability for next on-line FIM4L call - https://doodle.com/poll/28bwm5wzyu862gkd In the call we will discuss finalisation of FIM4L proto-charter - https://docs.google.com/document/d/17EllwItlnB3fYhJ2ZNpX6Z1gUfF1948ORRvtbIA… FIM4L guidelines and recommendations - https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy… and recent adoption of GEANT Data Protection Code of Conduct by RA21. Best regards Jiri Pavlik, Moravian Library

1 0

Fwd: [refeds] An announcement about RA21 and the Data Protection Code of Conduct
by Peter 05 Mär '19

05 Mär '19

Hi all, FYI. This aligns nicely with our recommendations... Cheers, Peter -------- Weitergeleitete Nachricht -------- Betreff: [refeds] An announcement about RA21 and the Data Protection Code of Conduct Datum: Thu, 28 Feb 2019 12:52:05 -0800 Von: Heather Flanagan <hlf(a)sphericalcowconsulting.com> Antwort an: refeds(a)lists.refeds.org An: refeds(a)lists.refeds.org Hot off the digital presses… https://ra21.org/index.php/2019/02/28/ra21-adopts-refeds-data-protection-co… Enjoy!

1 0

FIM4L update - projectstorage and new document
by Jos Westerbeke 26 Feb '19

26 Feb '19

Hi everyone, We set up a Google Team Drive where we can store our documents. The "proto-charter" and "guidelines" G-docs are already in it. Since we have G-suite at Erasmus university, we can offer this kind of storage (it's covered by much better "Terms of services" than the free version of Google docs). I would like to invite you all to this Team Drive. If you send me or Jiri your Google Gmail address, we can add you to our Team Drive "FIM4L workgroup", with edit rights. Once you have permission, the Team Drive will appear in your Google Drive<https://drive.google.com/>. And you can find all our files there. For those who don't want to get actively involved, we can/will let the public files stay public with access for everyone with the link plus comment. (not edit) Next step I'm trying to find out how we can start working towards our goal. Obviously, we have to define our goal first ;) Should our first goal be something like the following? - A reference with recommendations for establishing SSO authentication between libraries and publishers. It would be very beneficial for libraries if we could say to a publisher: "We want the establish SSO according the FIM4L recommendations, option 1, which you can find at <common FIM4L URL>." for example. Steps we can take: (supposedly) - Formulate a 'minimal disclosure policy'. - Build an 'SSO reference' for e-resource suppliers. - Build a FIM4L website/page where we can publish our recommendations/guidelines/references. Raoul already wrote a draft policy/recommendation/guideline based on the document and input from Jiri. Here is the new "FIM4L Guidelines and recommendations<https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy…>" document proposal by Raoul. (https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy… ) Jiri will add some more dates to the doodle poll<https://doodle.com/poll/rxemq8remn858qd7>. Please check it, and subscribe to be notified for any changes to the Doodle. There are still people coming on board, so we probably have to move the next meeting a bit forward. Feel free to comment on the text in the documents! What we have so far: FIM4L proto-charter<https://docs.google.com/document/d/17EllwItlnB3fYhJ2ZNpX6Z1gUfF1948ORRvtbIA…> (With the Problem Statement) FIM4L Guidelines and recommendations<https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy…> (new version) With kind regards Jos Jos Westerbeke Library IT Specialist / Demandmanager | Erasmus University Rotterdam, Library | Burgemeester Oudlaan 50 | 3062PA Rotterdam | jos.westerbeke(a)eur.nl<mailto:jos.westerbeke@eur.nl> | +31 640295513

5 7

FIM4L - notes meeting Feb.19
by Jos Westerbeke 21 Feb '19

21 Feb '19

Hi all, Thanks to all participants of the meeting last Tuesday and the help from others! We discussed three levels of attributes release: 1. transient ID - for maximum users privacy 2. persistent ID - for possibility to recognize returning users for (voluntarily) personalization and handling security incidents 3. persistent ID with personal identifiable information (PII) like name and e-mail - for the 'best' personalization We discussed what our case is all about. This could be narrowed to: "Access to licensed resources for libraries' staff and students." And we spoke about how to move on. The idea was to make our document more explicit coming weeks. Then we can write a new Position Paper to formalize our initiative. Again, don't hesitate to comment/write on the documents! All the best, Jos Jos Westerbeke Library IT Specialist / Demandmanager | Erasmus University Rotterdam, Library | Burgemeester Oudlaan 50 | 3062PA Rotterdam | jos.westerbeke(a)eur.nl<mailto:jos.westerbeke@eur.nl> | +31 640295513

1 0

Invitation: FIM4L call @ Tue 19 Feb 2019 10:00 - 11:00 (CET) (fim4l@lists.daasi.de)
by jos.westerbeke＠eur.nl 18 Feb '19

18 Feb '19

You have been invited to the following event. Title: FIM4L call Agenda: 1. Welcome 2. FIM4L proto-charter discussion 3. FIM4L guidelines and recommendations discussion 4. AARC 2 support: outreach assistance 5. AOB When: Tue 19 Feb 2019 10:00 – 11:00 Central European Time - Amsterdam Joining info: meet.google.com/ppq-dqwn-zgo <https://meet.google.com/ppq-dqwn-zgo> Calendar: fim4l(a)lists.daasi.de Who: * jos.westerbeke(a)eur.nl- organiser * fim4l(a)lists.daasi.de Event details: https://www.google.com/calendar/event?action=VIEW&eid=NXNmczNlcWo4Ymg1ZTZka… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account fim4l(a)lists.daasi.de because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively, you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to modify your RSVP response. Learn more at https://support.google.com/calendar/answer/37135#forwarding

1 0

Fwd: Survey launched from the RA21 Hospital Clinical Access Library Working Group!
by Jiri Pavlik 13 Feb '19

13 Feb '19

Hi all, you may like to take a part in this RA21 survey. BR Jiri ---------- Forwarded message --------- From: Julia Wallace <julia(a)ra21.org> Date: Tue, Feb 12, 2019 at 5:02 PM Subject: Survey launched from the RA21 Hospital Clinical Access Library Working Group! To: <announce(a)ra21.simplelists.com> Greetings from the STM RA21 Hospital Clinical Access Library Working Group <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fprotect-us…> ! We are conducting a study to learn the particular challenges and needs of hospital, health systems, and/or health center/clinic libraries with regard to authentication, technical support, and library resource access. This link https://www.surveymonkey.com/r/RA21_Survey <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.survey…> leads to an important survey comprised of about 20 questions. Can you help us? Please participate in the survey If you are a librarian serving a hospital or health care institution or in academia serving any type of health care institution. *If you choose to participate, you can also leave your contact information to be entered in a raffle to win one of four $50 Amazon gift cards. *The data you enter in the survey will be anonymized and will be used to inform: the final report of the “*RA21 Hospital Clinical Access Library Working Group,*” the work of the “*NISO RA21 Outreach Committee*” and a paper for MLA’s annual meeting in May, 2019. Many stakeholders are working to set up best practices, a new authentication standard and guidelines that addresses the needs of 21st century information seekers. We need to hear from you, your perspective is vitally needed! Thank you for your participation. Please feel free to forward this message to your medical librarian colleagues. Sincerely, Michelle Brewer, Librarian/Manager Market Intelligence, Wolters Kluwer ( michelle.brewer(a)wolterskluwer.com) Don Hamparian, Senior Product Manager, OCLC Catherine Dixon, MSLIS, Product Manager, Wolters Kluwer To unsubscribe from this list please go to http://www.simplelists.com/confirm.php?u=NIaVDGWHiuDtEQ2BRo6RLhZQc6DgC6pD

1 0

Next FIM4L call
by Jiri Pavlik 01 Feb '19

01 Feb '19

Dear all, Doodle poll for next FIM4L call is prepared - https://doodle.com/poll/rxemq8remn858qd7 Thanks a lot to Jos and Raoul for adding problem statement and comments to FIM4L proto-charter - https://docs.google.com/document/d/17EllwItlnB3fYhJ2ZNpX6Z1gUfF1948ORRvtbIA… There is new FIM4L guidelines and recommendations draft you can review, comment, edit - https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy… Best regards Jiri Pavlik, Project AARC / Moravian Library

4 6