Group 1

From Library Freedom Wiki Page
Jump to navigation Jump to search

Group 1's Collaborative Space

Group 1: Michele Alaniz, Nicole Becwar, Symphony Bruce, Michelle Nitto, Jonathan Hernandez, Qiana Johnson, Junior Tidal, (academic librarians)

Graphic design needs

To Do

Notes 7.05.19

SB will draft language to tie everything/theme together. *Done*

Communicate more frequently not via email

Set up a calendar/timeline via shared document *Done*

SB will create a shared folder and connect to the wiki. *Done*

MN recommends not using GSuite

Decide timeline of the project within the next week via Google Doc. *Created*

Try to finish a bulk of work by mid-August.

Maybe possible to meet at the in-person and work on the project.

Schedule a Zoom meeting before we're in NYC.

MA will talk to Alison re: group update. [I think we can just follow the format that we see listed in "small group progress" thread along with Symphony's introduction - also would like to send out a poll so that we can get a decision on group name, or we can decide next time we talk. MA)

- Maybe we can come up with a fun group name?

Ideas: Anony-moose? The Privacy Avengers? EndPlatformCapitalism? OK(No)Google?

===Draft Group Outline===

Objective: Create a series of classes and tools to inform specific communities regarding privacy concerns in recognition of Privacy Week.

Timeline: Complete a bulk of the project by the end of August before the semester starts.

Roles: Each person responsible for a component will have periodic check-ins (weekly?) on progress.


  • Use the Wikipage to comment and check-ins to avoid too many emails?

Below is a programing plan in recognition of Privacy Week on an academic campus. Our goal is to provide programming in a variety of outputs for a variety of stakeholders. With this variety in mind, the programming components below represent the needs of administrators, librarians, instructors, students, and campus information technology professionals. Each group member will present an option to reach one of these groups.

The components created by each group member will also be presented in a variety of formats, like in-person classes versus text-based materials. In an effort to promote our Privacy Week programs, each group member will also offer an idea to add to a display.

Group project ideas

1. Privacy class or tutorial for students w/ a corresponding module - Junior [Draft outline]

Ideas (can be recycled for other projects below):

  • Audience: college students
  • Evaluating one's privacy concerns (threat assessment but not in those terms).
  • Password exercise using diceware
    • Discussion about phishing and spamming
  • FBI/ICE/Police using social media to harvest information for incriminating purposes.
  • Discussion about metadata as it pertains to social media & geography (ie taking pictures w/ your Smartphone).
  • Search engines/adware/e-commerce tracking first-party/third-party data collection via cookies.

2. Privacy class/tutorial/workshop/training for instructors for incorporating privacy instruction – help them make better choices about what types of systems/app that they ask their students to use in coursework - Michele A. [Draft outline]


  • Audience: Instructors


  • Blackboard
  • Canvas
  • Vendors: Cengage, Proquest (e.g. Safari Tech Books),
  • Google for Education
  • TurnItIn
  • Grammarly

Search (include elements from student focused privacy tutorial):

  • Search engines/adware/e-commerce tracking first-party/third-party data collection via cookies.

Privacy instruction for educators (what do we want them to know?)

  • What type of information can be collected?
  • Protecting student privacy because of intellectual freedom/making students aware of how companies making profit from their data and work(maybe?)

Maybe we could add some privacy advice on messenger and video communications apps (Whatsapp, Zoom, etc) - JH

3. Vendor agreement or privacy policy (Perhaps particularly as it relates to library materials) - Qiana & Nicole


  • Negotiating vendor agreements to include privacy policy
  • RELX group and Thomson & Reuters have shady business deals with DHS - read paper:
  • vendor privacy policies are often composed of very vague language i.e. "we may collect this if you use our service in this way" - it is unclear how this data is being stored, assessed, and even shared with other companies.
    • vague language in policies enables private companies to proclaim transparency while not really fully explaining the lifecycle of how they collect and analyze student/university data
  • What data do vendors collect? (beside IP addresses?)

4. Guidebook for students - for when they are victims of online harassment - Symphony

  • Audience: students
  • Anti-doxx tools
  • Digital footprint - where personal info is stored, how to get request deletion
  • Scrubbing social media?
  • DIY digital forensics on oneself? (Who is harassing me?)
  • Anti-social hacking awareness (Ex.Don't give out the name of your dog to strangers who may hack your social media using password questions, etc.?)
  • Carolyn Sinders gave a lecture re: online harassment
  • Discussion differentiating harassment, bullying, and gossip.

5. Display about privacy (as a marketing tool for Privacy Week Programming) - can be used as a theme to tie everything together. Can be used to market as for a colloquium. ((*Book/media (films, documentaries, etc.) display

  • Zine(s):
    • local surveillance issues (ex. how are cops psying on us?, what is the federal government doing with our data & how do they obtain it from ISPs/ telecomm providors?)
    • what does my iphone know about me? (ex. my location, my habits, my moods, etc.) - this can be in a format where it is blank and with questions and directions and then students fill it out
    • what does facebook/instagram think that they "know" about us? (ex. how to discover which categories you have been placed into by this megacompany) - this can be in a format where it is blank and with questions and directions and then students fill it out)) - *Info will need to be edited and changed to our individual contributions** - SB
  • add your thoughts about new language or methods for threatmodelling or teaching others what a threat model is here:

Notes: Guidebook or tool could be integrated into the workshops.