[aisle] Interested in testing Privacy Advocacy Guides?

[Lou Ann Jacobs]

The following message was originally posted on the AASL Forum. Further
emails asked that this be shared by state affiliates with their members.

Lou Ann Jacobs
AISLE Legislation

-----Original Message-----
From: Helen Adams <aaslforum at lists.ala.org>
To: aaslforum <aaslforum at lists.ala.org>
Sent: Sat, Sep 7, 2019 9:27 am
Subject: [aaslforum] Interested in testing Privacy Advocacy Guides?

Hello AASL Members,
The Alameda County Library (Oakland, CA), the American Library
Association's Office of Intellectual Freedom, and the Data and Society
Research Institute have received an IMLS grant to create web-based and
print *Privacy Advocacy Guides*. The primary goal of the guides is to help *all
types of librarians* become privacy advocates for their library users.
The guides will provide librarians with:
·         Clear guidelines and discussion points for engaging with
administrators, vendors, school boards, parents, and other stakeholders
about privacy-related topics and
·         Information that will lead to libraries creating privacy
policies, performing audits, negotiating privacy conscious vendor
contracts, and educating users about privacy and security.
In reaching out to AASL members, the grant team is seeking school
librarians in districts of all sizes, both urban and rural, that would like
to test these new guides. There are no requirements other than a commitment
to try out the Privacy Advocacy Guides and give feedback. The project team
is anticipating launching the guides at test sites in February and running
the test for several months.
If you are interested or have questions, contact Erin Berman, Alameda
County Library, by email at ErinBerman at aclibrary.org or by phone at
510-745-1520.
Helen Adams
ALA Privacy Subcommittee member
ALA Intellectual Freedom Committee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.railslibraries.info/pipermail/aisle/attachments/20190909/4e381c09/attachment.html>