For years, libraries across America have paid to subscribe to lynda.com for online learning content; four years ago, lynda.com became a division of Linkedin, and this year, the company has informed libraries that they're migrating all lynda.com users to Linkedin Learning, which would be fine, except Linkedin only allows you to access Linkedin Learning if you create and connect a Linkedin profile to the system.
If libraries accept this change, it will mean that any patron who uses this publicly funded service will also have to have a publicly searchable Linkedin profile. Linkedin's explanation of why this is OK is purest tech-bro PR bullshit, condescending and dismissive.
Libraries are fighting back: California State Libraries is recommending that libraries boycott the service, and the American Library Association has publicly condemned the move.
If you work in a library and want to give feedback to Linkedin about this, the right person to email is Farhan Syed, Vice President of Client Solutions, whose email address is firstname.lastname@example.org.
ALA has long affirmed that the protection of library users' privacy and confidentiality rights are necessary for intellectual freedom and are fundamental to the ethical practice of librarianship. ALA's Library Bill of Rights and its interpretations maintain that all library users have the right to access library resources without disclosing their personally identifiable information (PII) to third parties, and to be free from unreasonable intrusion into, or surveillance of, their lawful library use.
"The requirement for users of LinkedIn Learning to disclose personally identifiable information is completely contrary to ALA policies addressing library users' privacy, and it may violate some states' library confidentiality laws," said ALA President Wanda Kay Brown. "It also violates the librarian's ethical obligation to keep a person's use of library resources confidential. We are deeply concerned about these changes to the terms of service and urge LinkedIn and its owner, Microsoft, to reconsider their position on this."