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.
There's a fine line between affecting change through mobilizing your followers and affecting change through weaponizing your followers. Intent and impact both matter in that fine line division.
There's more I want to say about this, but the topic is probably better suited for a blog post.
Platform building, the various natures of follower bases, & power dynamics between poster/user and their follower base have been rummaging around the back of my mind for a long while.
Tho I just remembered the time where a librarian chased another librarian *across platforms* while attacking this person for not doing enough even after this person stated very valid life reasons as to they hadn't been able to do more at the time.
And now I'm mad all over again.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
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.
Libraries do not have leverage when there is a near monopoly in the ILS marketplace.
Also libraries never really had leverage given how each proprietary ILS is designed for complete lock in making it extremely difficult to do anything outside of that particular vendor ecosystem.
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.
Now imagine that a library was asked to keep a patron visitor log for contact tracing.
Depending on the state's library confidentiality laws, this information is protected from disclosure. But again, the library now has created a paper trail of a patron's use of the library.
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.
[Guess which one is "sexy" and the other "not"?]
[Tangent - I still encounter the use of the word "sexy" w/r/t tech and metadata work. The fact that people still view objects and ideas as sexually desirable tells you a lot about the values of the people assigning said desirability as well as the audience for said comment.]