Good morning, Eastern Australia! Just posted my #VALA2024 talk "The Interdependent Library System: Revisiting Human Aspects of Library Automation"

https://ruthtillman.com/talk/interdependent-library-system/

on my personal website. Getting my slide deck fixed up to send to the conference tomorrow.

The Interdependent Library System: Revisiting Human Aspects of Library Automation | Ruth Kitchin Tillman

What does it mean to consider the "human aspects of library automation" when we approach a migration or other technological shift in the workplace? In this talk, I reflect on the contexts and experiences of workers over the history of library technology and share preliminary insights from my research.

Ruth Kitchin Tillman
@platypus A fantastic talk to read, so I'm sure the people who got to hear it delivered had a real treat. I especially appreciate the "people who have complaints about the new thing are not afraid of it, they're trying to tell you their workflow has changed and that's worth paying attention to." Part of the public interactions I have are often "I used to be able to do this, then they changed where everything goes and I can't find anything any more."
@TheyOfHIShirts that makes a lot of sense! I can see a lot of ways that’d be fielded when engaging with the public, from library specific stuff to questions about how bigger things work (software, local govt, etc)

@platypus Yep. I do a lot of walking people through various things, and occasionally I go "I know it can be done, but how do I do it on this version of this software?" and look it up. I think it may be comforting to some of them that even the person who is a supposed guru of things still has to look things up.

And, actually, while I didn't do an ILS migration this year, I got access to the browser-based tool that will eventually replace the client, and my workflows have changed just from that.

@TheyOfHIShirts BlueCloud?
@platypus Leap, from III's Polaris.
@TheyOfHIShirts oh interesting!! I don’t follow Polaris as closely because we definitely won’t be buying it, but the whole β€œweb client for same ILS” has been interesting
@TheyOfHIShirts nothing inherently wrong with Polaris just not for academics whereas Sirsi Symphony is widely used in publics and has been at least in academics

@platypus Yeah. Although the publics around me have basically the same discovery layer on top of very different ILSes, so that's interesting.

I find that my weeding process was assisted by some of the data displays of the old client and Leap does not replicate that display, even if it shows the same data. It takes me many more clicks to get the information that I used to be able to just set on my desktop and let it change with each new scanned barcode. It's bothersome and it slows me down.

@TheyOfHIShirts yeah -- there's a kind of infinite world in there, like, if you don't change staff interfaces what's still possible with front-end? We run the same thing as Princeton and for a while they were using Voyager and we were using Symphony, now they're on Alma and their catalog/discovery looks pretty similar, whereas we're still on Symphony. And then there's the vended versions like bibliocommons.
@platypus It's all bibliocommons around me, even though the backends are Evergreen, Polaris, possibly a Sirsi somewhere, and it makes me wonder what it's like for them, and if bibliocommons offers them workflows to do things that they can put back in databases, or whether they're strictly pulling from databases and displaying them. And how much cognitive juggle it is for people who have to remember what the public-facing end can do versus the staff-facing end, and which tasks use which tools.