{"id":910,"date":"2015-01-30T12:54:52","date_gmt":"2015-01-30T20:54:52","guid":{"rendered":"http:\/\/galencharlton.com\/blog\/?p=910"},"modified":"2015-01-30T12:54:52","modified_gmt":"2015-01-30T20:54:52","slug":"putting-my-time-where-my-mouth-is-on-the-patron-privacy-front","status":"publish","type":"post","link":"https:\/\/galencharlton.com\/blog\/2015\/01\/putting-my-time-where-my-mouth-is-on-the-patron-privacy-front\/","title":{"rendered":"Putting my time where my mouth is on the patron privacy front"},"content":{"rendered":"

Shortly after it came to light that Adobe Digital Editions was transmitting information about ebook reading activity in the clear, for anybody to snoop upon, I asked a loaded question<\/a>: does ALA have a role\u00a0in helping to verify that the software libraries use protect the privacy of readers?<\/p>\n

As with any\u00a0loaded question, I had an answer in mind: I do think that ALA and LITA, by virtue of their institutional heft\u00a0and influence with\u00a0librarians, can provide significant assistance in securing library software.<\/p>\n

I waited a bit, wondering how\u00a0the powers that be at ALA would respond. Then I remembered something: an institution like ALA is not, in fact, a faceless, inscrutable\u00a0organism. Like Soylent Green, ALA is people!<\/p>\n

Well, maybe not so much like Soylent Green. My point is that despite ALA’s reputation for being a heavily bureaucratic, procedure-bound organization, it\u00a0does<\/em> offer ways for members to take up and idea an run with it.<\/p>\n

And that’s what I did — I floated a petition to form a new interest group within LITA, the Patron Privacy Technologies IG. Quite a few people signed it… and it now lives<\/a>!<\/p>\n

Here’s the charge of the IG:<\/p>\n

The LITA Patron Privacy Technologies Interest Group will promote the design and\u00a0implementation of library software and hardware that protects the privacy of library users and\u00a0maximizes user ability to make informed decisions about the use of personally identifiable\u00a0information by the library and its vendors.<\/p>\n

Under this remit, activities of the Interest Group would include, but are not necessarily limited to:<\/p>\n

    \n
  1. Publishing recommendations on data security practices for library software.<\/li>\n
  2. Publishing tutorials on tools for libraries to use to check that library software is handling\u00a0patron information responsibly.<\/li>\n
  3. Organizing efforts to test commercially available software that handle patron information.<\/li>\n
  4. Providing a conduit for responsible disclosure of defects in software that could lead to\u00a0exposure of library patron information.<\/li>\n
  5. Providing sample publicity materials for libraries to use with their patrons in explaining the\u00a0library\u2019s privacy practices.<\/li>\n<\/ol>\n<\/blockquote>\n

    I am fortunate to have two great co-chairs, Emily Morton-Owens of the Seattle Public Library and Matt Beckstrom of the Lewis and Clark Library, and I’m happy to announce that the IG’s first face-to-face meeting<\/a> will at ALA Midwinter 2015 — specifically \u00a0tomorrow, at 8:30 a.m. Central Time in the Ballroom 1 of the Sheraton in Chicago.<\/p>\n

    We have two great speakers lined up — Alison Macrina of the Library Freedom Project and Gary Price of INFODocket, and I’m very much looking forward to it.<\/p>\n

    But I’m also looking forward to the rest of the meeting: this is when the IG will, as a whole, decide how far to reach. \u00a0We have a lot of interest and the ability to do things that will teach library staff and our patrons how to better protect privacy, teach library programmers how to design and code for privacy, and verify that our<\/strong> tools match our ideals.<\/p>\n

    Despite the title of this blog post… it’s by no means my effort alone that will get us anywhere. Many people are already engaging in issues of privacy and technology in libraries, but I do hope that the IG will provide one more point of focus for our efforts.<\/p>\n

    I look forward to the conversation tomorrow.<\/p>\n

    Share this:<\/h3>