Editing Main Page/Crash Courses/Systems and Policies/Week three

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
=== Week 3: Privacy policies and best practices ===
+
=== Week 3: Privacy policies ===
* Real time conversation: March 15th 8:30 - 10:30 Pacific/11:30 - 1:30 Eastern on Zoom https://zoom.us/j/9129428892
+
* Real time conversation: June 3rd 9:30 - 11:30 Pacific/12:30 - 2:30 Eastern on Zoom https://zoom.us/j/9129428892
* Recording: https://vimeo.com/688514606
 
  
 
==== Overview ====
 
==== Overview ====
While library workers have long considered privacy as a core value of librarianship, our practices often leave a lot to be desired. Strong privacy policies can be a foundation on which better privacy practices are built. This week, we'll talk about the components of a good privacy policy, addressing things like data collection and storage, law enforcement requests, futureproofing, and US state laws governing library records. We'll also discuss implementing privacy policies, as well as patron education.
+
 
 +
this is the week we should also talk about best practices for low-level stuff, eg hold slips, phone calls about patrons how this ties into the policy stuff
 +
 
 +
While librarians have always considered privacy among our most sacred core values, our in-library practices leave a lot to be desired. Recent privacy issues with vendors like Kanopy, Lynda.com, and Gale Analytics have brought to light the abysmal privacy practices of library vendors. And while it's easy to criticize these outside parties, our internal privacy policies could also use a lot of work.  
 +
 
 +
This week, we'll hear from four Library Freedom Privacy Advocates about their work on vendor privacy and internal privacy polices. Qiana Johnson and Nicole Becwar from cohort two will discuss how vendors measured up against the privacy prompts in their vendor scorecard (see readings). Then Jessica Krill and Tracy Treece (also cohort two) will discuss how they created their privacy policy template (see readings) and how librarians can put it into place.  
  
 
==== Readings ====
 
==== Readings ====
* LFP library privacy policy template: https://docs.google.com/document/d/1a9n2SAYLua0ELQzAcJtbfpxWg2MRkucL7sM92aniNMo/edit#heading=h.9v96ldaenxun
+
* Vendor privacy scorecard: https://github.com/alisonLFP/libraryfreedominstitute/blob/master/LFI2/finalprojects/Library%20Freedom-%20Vendor%20Scorecard-%20110719.pdf
* ALA guidelines on developing or revising a privacy policy http://www.ala.org/advocacy/privacy/toolkit/policy
+
* Why vendor privacy Q&A (click the download button on github): https://github.com/alisonLFP/libraryfreedominstitute/blob/master/LFI2/finalprojects/WhyPrivacyLicenseQ%26A-Qiana_Nicole.docx
 +
* Library privacy policy template: https://docs.google.com/document/d/1a9n2SAYLua0ELQzAcJtbfpxWg2MRkucL7sM92aniNMo/edit#heading=h.9v96ldaenxun
 
* ALA Library Privacy Checklists: http://www.ala.org/advocacy/privacy/checklists
 
* ALA Library Privacy Checklists: http://www.ala.org/advocacy/privacy/checklists
 
* Protecting Patron Privacy: Librarians, Vendors, and Patrons Each Have a Role to Play: https://digitalcommons.du.edu/cgi/viewcontent.cgi?article=1330&context=collaborativelibrarianship
 
* Protecting Patron Privacy: Librarians, Vendors, and Patrons Each Have a Role to Play: https://digitalcommons.du.edu/cgi/viewcontent.cgi?article=1330&context=collaborativelibrarianship
* State privacy laws regarding library records: http://www.ala.org/advocacy/privacy/statelaws
+
* San Jose Public Library Vendor Security Analysis results: https://drive.google.com/open?id=1jdPwQeC5RAUbBWLAhyIYxWHa0pTdVObc
* State consumer privacy laws: https://www.ncsl.org/research/telecommunications-and-information-technology/state-laws-related-to-internet-privacy.aspx
+
* EFF’s How to Assess Vendors’ Data Security: https://www.eff.org/deeplinks/2018/01/how-assess-vendors-data-security
* Read your own library's privacy policy (or another library's privacy policy of your choosing)
 
  
==== Discussion prompt ====
+
==== Guest lecturer ====
* How does your library's policy (or the policy you chose) measure up to the best practices? (note: you don't have to identify the library in the discussion)
 
* What challenges might you face trying to update your library's policy to meet best practices? Implementation? Enforcement? Making the policy a priority at all?
 
  
 +
==== Discussion ====
 +
* What are the elements of a good privacy policy?
 +
* Enforcement
 +
* ideas for getting started
 +
* ideas for future action
  
 
==== Tasks ====
 
==== Tasks ====
 
* Lecture, readings, discussion forum
 
* Lecture, readings, discussion forum
 +
* Schedule final project checkin with Alison
 +
 +
 +
Making good privacy/data governance policies, more privacy language, and best practices
 +
 +
 +
 +
Library privacy policy template: https://docs.google.com/document/d/1a9n2SAYLua0ELQzAcJtbfpxWg2MRkucL7sM92aniNMo/edit#heading=h.9v96ldaenxun
 +
ALA Library Privacy Checklists: http://www.ala.org/advocacy/privacy/checklists
 +
Protecting Patron Privacy: Librarians, Vendors, and Patrons Each Have a Role to Play: https://digitalcommons.du.edu/cgi/viewcontent.cgi?article=1330&context=collaborativelibrarianship
 +
 +
https://twitter.com/KyleKCourtney/status/1384875670363385857

Please note that all contributions to Library Freedom Wiki Page may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Library Freedom Wiki Page:Copyrights for details). Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)