[OPLINLIST] Lynda.com to LinkedIn Learning transition

[Nicholas Slone]

Last night, our board voted unanimously to withdraw participation in 
Lynda/LinkedIn Learning.

ALA's privacy sub-committee has provided information about potential 
replacement e-learning platforms 
<https://chooseprivacyeveryday.org/online-learning-platforms/> on their 
Choose Privacy Every Day <https://chooseprivacyeveryday.org/> site.

If anyone, in addition to the OPLIN board, would like to get a copy of 
the email I'm sending to our current Lynda users, please let me know. 
For those that also choose to withdraw participation, Erin Berman, chair 
of ALA's privacy subcommittee, asks that you let her know, as she's been 
compiling a list of libraries for several weeks, now. Her email address 
is ErinBerman at aclibrary.org.

Sincerely,
Nicholas Slone
Executive Director
Adams County Public Library

On 8/10/2019 12:29 PM, Don Yarman via OPLINLIST wrote:
> At their meeting Friday, August 8, the OPLIN Board reviewed the new 
> LinkedIn Learning for Libraries terms of use 
> (https://legal.linkedin.com/service-specific-terms) and discussed the 
> limited access that OPLIN staff will have to the administrator 
> accounts for the service. They reiterated that, although the situation 
> is not ideal, the high usage of the Lynda.com content and the value of 
> that resource to Ohioans is such that OPLIN will continue to support a 
> statewide agreement.
>
> LinkedIn is only now conducting their beta-tests of the new platform 
> for libraries, but time grows short. They intend to move all library 
> customers onto the new platform within the next couple months. I am 
> meeting with their project team early in the week to hammer out 
> specifics, and I will communicate details as soon as I have them. I do 
> know at this point that the first libraries to migrate will be those 
> using the Sierra ILS; those libraries will be hearing from us soon 
> about requirements for the platform change.
>
> One of the requirements is that each of the old Lynda admin accounts 
> will have its functions transferred to an individual’s LinkedIn 
> profile. In most cases, the current Lynda admin accounts are 
> associated with directors’ email addresses, but the LinkedIn Learning 
> admin functions do not have to be in the director’s LinkedIn account: 
> they can be delegated to another staff member. This must be a library 
> employee's personal LinkedIn account; LinkedIn does not allow shared 
> profile access, nor do they allow multiple administrators for LinkedIn 
> Learning for Libraries.
>
> I am sure you have read the statements from ALA and other 
> organizations protesting LinkedIn’s plans. I know there are Ohio 
> libraries that have signed onto these statements. If your library does 
> not wish to move patrons onto the new platform, OPLIN will honor that 
> request. The library director will need to send an email to me or to 
> support at oplin.ohio.gov <mailto:support at oplin.ohio.gov> telling us not 
> to set up your library on the new platform. (If you would like to add 
> your reasons, the OPLIN Board is interested in knowing them. They are 
> also interested in any patron feedback you receive concerning 
> Lynda.com/LinkedIn Learning.) If you opt out, your patrons will remain 
> on the existing lyndaLibrary platform until those servers are 
> decommissioned December 31, 2019.
>
> As a reminder, more information about this change is posted at 
> https://oplin.ohio.gov/lynda-transition. I will continue to update 
> that page as new information becomes available.
>
> Don Yarman
>                     Director, Ohio Public Library Information Network
>                     2323 W Fifth Ave Suite 130, Columbus OH 43204
> don at oplin.ohio.gov <mailto:don at oplin.ohio.gov> | 614.728.5250
>
> _______________________________________________
> OPLINLIST mailing list -- OPLINLIST at lists.oplin.org
> http://lists.oplin.org/mailman/listinfo/oplinlist
>
> *** Does your staff need phishing and security awareness training? Find out more:    https://www.oplin.ohio.gov/securityiq ***
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.oplin.org/pipermail/oplinlist/attachments/20190815/87e2b805/attachment.html>