[Fim4l] FIM4L update - projectstorage and new document

Peter peter.gietz at daasi.de
Mon Feb 25 17:12:42 CET 2019


Dear all,

first of all sorry, that I again couldn't make the meeting. I came back
from vacation quite ill and am still recovering.

As to the recommendations, I would be more careful and delete the last
bullet. For personalization the targetedID is sufficiant. If the
publishers want to adress the customer by name, they can ask for the
name themselves.

Cheers,

Peter

Am 15.02.19 um 10:59 schrieb Jiri Pavlik:
> Dear all,
>
> I'd suggest to add following guidelines for libraries, universities at
> our FIM4L Guidelines and recommendations:
>
> - register IdP in eduGAIN
> - support CoCo and SIRTFI
> - release NameID/eduPersonTargetedID, eduPersonScopedAffiliation,
> schacHomeOrganisation, eduPersonEntitlement 
>   to publishers SPs as basic set of attributes allowing publishers to
> carry out authorisation, handling security incidents
>   and provide personalisation
> - release other attributes such as Display/Common name or Email
> described in the eduGAIN Attribute Profile
>   for the best user experience with personalisation of a service
>
> Looking forward to discuss it in our call, so far Tuesday next week
> 10-11 is the best fit - 
>    https://doodle.com/poll/rxemq8remn858qd7
>
> Sunny regards from Prague
>
>            Jiri
>
>
>
> On Wed, Feb 13, 2019 at 10:03 AM Jiri Pavlik <jiri.pavlik at mzk.cz
> <mailto:jiri.pavlik at mzk.cz>> wrote:
>
>     Dear all,
>
>     I added more time slots for FIM4L next call in the Doodle poll -
>     https://doodle.com/poll/rxemq8remn858qd7
>     There are also Europe late afternoon time slots so American
>     colleagues could join us for the call in not so early
>     morning hours.
>
>     Thanks a lot Jos, for the update and Raoul for the recommendations
>     and guidelines draft.
>
>     Best regards
>
>                  Jiri
>
>
>     On Fri, Feb 8, 2019 at 12:45 PM Jos Westerbeke
>     <jos.westerbeke at eur.nl <mailto:jos.westerbeke at eur.nl>> wrote:
>
>         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/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy2nck/edit>"
>         document proposal by Raoul.
>
>         (https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy2nck/edit
>         )
>
>         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_l88/edit>
>         (With the Problem Statement)
>
>         FIM4L Guidelines and recommendations
>         <https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy2nck/edit>
>         (new version)
>
>          
>
>         With kind regards
>
>         Jos
>
>          
>
>         Jos Westerbeke
>
>         Library IT Specialist / Demandmanager  | Erasmus University
>         Rotterdam, Library | Burgemeester Oudlaan 50 | 3062PA
>         Rotterdam | jos.westerbeke at eur.nl
>         <mailto:jos.westerbeke at eur.nl> | +31 640295513
>
>          
>
>         _______________________________________________
>         Fim4l mailing list
>         Fim4l at lists.daasi.de <mailto:Fim4l at lists.daasi.de>
>         http://lists.daasi.de/listinfo/fim4l
>
>
> _______________________________________________
> Fim4l mailing list
> Fim4l at lists.daasi.de
> http://lists.daasi.de/listinfo/fim4l
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.daasi.de/pipermail/fim4l/attachments/20190225/8eb9d405/attachment.html>


More information about the FIM4L mailing list