Mastodon - @yo_bj@glammr.us
Privacy Consultant. Battle-hardened Systems Librarian. Forever a Cataloger. Cat assistant. She/her. CIPP/US. CIPT. https://t.co/9rl1k40Y3f
Jul 21, 2022 • 12 tweets • 3 min read
Library workers - if you are looking for guidance about what you can do *now* to protect patron privacy while patrons search and browse online at the library, here is the guide to get you started!
chooseprivacyeveryday.org/guidelines-for…
The guidelines are a starting point - taking 5 minutes to go through the guidelines & identifying areas in which you can harden data privacy/security protections will go a very long way.
Never underestimate the power of doing even the smallest of things - they add up over time.
Jul 21, 2022 • 4 tweets • 2 min read
Having the option to opt out won't protect students who are already abused or neglected (or are at high risk of abuse or neglect) at home.
This is especially disappointing coming from a library journal that is highly respected because of the editorial care usually put into review and publication.
Defend your author instead of leaving them without backup.
You decided to go ahead with publication. You decided to double down just now.
Editorial boards are not neutral.
Mar 25, 2022 • 9 tweets • 3 min read
If you are a Follett Destiny library, now would be a very good time to talk to them about your concerns about the option being built into the systems that you and your students use.
Here's an additional write-up that gets more into the details of the upcoming Destiny changes: forsythnews.com/news/education…
[Image text in alt text]
Feb 23, 2021 • 14 tweets • 3 min read
One of my professional colleagues sent me a library vendor privacy policy last week & asked about some questionable practices in the policy.
What came next is a cautionary tale of the murkiness that is library vendor privacy policies in a time of company acquisitions.
🧵
The policy in ? is iii.com/services-priva…. III has 2 privacy policies, but this one covers the services & most products sold by III, including discovery layers, mobile apps, content management, & APIs.
If you are a III customer, it might behoove you to read the policy. 2/n
Jan 28, 2021 • 7 tweets • 2 min read
The amount of technical debt from our reliance on proprietary ILSes to serve as the core of library operations makes the effects of the consolidation of the ILS market that much worse.
To add - you don't necessarily need to have a solution at the ready when you criticize something. However, it's one thing to point out issues and another to habitually tear down the people trying to do the work while pointing out said issues.
On a related #LibraryTwitter note, it's 1 thing to use the platform that you built on here to put issues on people's radar. It is another to weaponize your platform to tear down individuals who are trying to do the work to the point where they have to lock or leave their account.
May 12, 2020 • 15 tweets • 4 min read
Now that WA restaurants have to keep logs w/customer names & contact information, I'm wondering when libraries are going to be asked by the gov to have a similar log for anyone visiting the library as part of the reopening process.
This restaurant log is mainly for contact tracing, which is a tried and true way of reducing infections in a population in previous outbreaks.
However, that doesn't erase the fact that the restaurant now has more data on their customers that they wouldn't have had before.
Mar 30, 2020 • 5 tweets • 2 min read
Working from home only means one thing - more web meetings! However, are you sure that the Zoom session you're holding will not put library data privacy at risk? How can you use Zoom and still protect patron privacy? Learn more in this week's newsletter - ldhconsultingservices.com/newsletter-arc…
One thing that didn't make it in today's newsletter is that Zoom did a MAJOR privacy policy overhaul in the last 24 hours - zoom.us/privacy
I get that folks want MARC to die, & the process of getting a replacement is taking forever.
However, telling folks that worked w/MARC & other forms of cataloging standards that they have nothing valuable to contribute to the "metadata ecosystem" is a red button topic of mine.
Part of it comes from the unspoken pairing of metadata w/technology, and cataloging w/traditional librarianship, and how gender and power dynamics play in these pairings in our discussions around description and organizing info.
