| Latest revision |
Your text |
| Line 1: |
Line 1: |
| − | = Library Privacy Policy Working Group = | + | === Library Privacy Policy Working Group === |
| − | == Current Work in Progress ==
| |
| − | * Sample process framework being developed (Jen, Mack)
| |
| − | * Sample talking points (Alison)
| |
| − | * Establishing meeting schedule (Mark)
| |
| − | | |
| − | == Talking points ==
| |
| − | * Ethics/core values: Privacy is one of our core values, and is fundamental to so many of our other values like intellectual freedom and access. If we’re failing to consider privacy, we’re failing at the foundational principles of librarianship.
| |
| − | ** Alison will be adding a few expanded points to each of these categories.
| |
| − | * Legal compliance: Many states require library record confidentiality by law, and good privacy policies can help us be compliant with the law.
| |
| − | * Data stewardship: Libraries have a lot of patron data, and a strong privacy policy can help us be good stewards of this data: understanding what we have, what we keep, for how long, what we’ll do in the event of a data breach, and so on.
| |
| − | * New services/software: A good privacy policy can help us evaluate potential new software and services.
| |
| − | * Policy for crisis management: A good privacy policy can help under stress, eg if we receive a data request from law enforcement.
| |
| − | * Policy into practice: Policy creation is an opportunity to reflect on practice, and perhaps a good time to conduct a privacy audit of all library services and systems.
| |
| − | * Staff training: Privacy policy enforcement can be made easier if staff are regularly trained on library values.
| |
| − | * Patrons: Privacy policies should cover all library services and systems, but also be simple and readable so that patrons and staff can easily understand them.
| |
| − | * IT talking point (security focused)
| |
| − | * General privacy talking point
| |
| − | | |
| − | == Resources ==
| |
| − | * [https://drive.google.com/file/d/1WZNx4zsw9hjHdUfGBMM1dlStJSdMn44W/view LFI Crash Course presentation]
| |
| − | * [https://libraryfreedom.wiki/html/public_html/index.php/Main_Page/Crash_Courses/Systems_and_Policies/Week_three Cohort 3 notes]
| |
| − | * [https://docs.google.com/document/d/1a9n2SAYLua0ELQzAcJtbfpxWg2MRkucL7sM92aniNMo/edit LFI Privacy Policy Guide]
| |
| − | | |
| − | == Sample Privacy Policies ==
| |
| − | * [https://www.nypl.org/help/about-nypl/legal-notices/privacy-policy NYPL privacy policy]
| |
| − | * [https://www.nypl.org/help/about-nypl/legal-notices/privacy-policy/faq NYPL privacy policy FAQ]
| |
| − | | |
| − | == Meeting Minutes ==
| |
| − | | |
| − | === 9/28/21 ===
| |
| − | * Jen started this process framework document: https://docs.google.com/spreadsheets/d/1dPwzyfBdhlOSyf-LAcRYSBMDCoPRdMMcHuQjaSbox9Q/edit?usp=sharing
| |
| − | * Mack is going to take on the next step of adding process framework
| |
| − | * Alison is going to expand on the talking points
| |
| − | * Everyone is going to continue looking into privacy policies and add the good ones here
| |
| − | | |
| − | === 9/2/21 ===
| |
| − | 9/2/21, 10am EDT
| |
| − | * Attendance
| |
| − | ** Alison Macrina
| |
| − | ** Jen Wilson
| |
| − | ** John Mack Freeman
| |
| − | ** Mark Swartz
| |
| − | ** Ashley Teagle
| |
| − | ** Marisol
| |
| − | ** Ayoola
| |
| − | * Introductions
| |
| − | * Review of previous notes and needs
| |
| − | * Where to go from here
| |
| − | ** Talking points for colleagues to get started with
| |
| − | *** Getting library boards and lawyers involved
| |
| − | *** Expressing value of the effort and people time
| |
| − | *** Why making it simple, understandable, and effective is important
| |
| − | *** Potential talking points
| |
| − | **** Alison will take point on this. First draft coming within the next week.
| |
| − | **** Doing this work well at the outset takes work, but if it’s done well, it will just work and won’t require ongoing work
| |
| − | ** What is step one
| |
| − | *** Document what starting this process is
| |
| − | *** JEN WILSON: What are the first steps at your institution so we can build a listing of potential pathways? Creating a basic framework with potential holes and marking potential pain points
| |
| − | **** Consider notating role of the person writing the path for generalizability
| |
| − | ** Considering how to present this process
| |
| − | *** Graphic design
| |
| − | *** Chunking/challenge approach
| |
| − | * Notate along the way what can be generalized verses what is specific
| |
| − | ** Academic vs. Public, small vs. big, bureaucratic vs. free-form
| |
| − | | |
| − | | |
| − | === 7/29/21 ===
| |
| | * 7/29/21, 3pm EDT | | * 7/29/21, 3pm EDT |
| | * Attendance | | * Attendance |
