Categories
conference Libraries

Library Issues Round Table

Whoops – this should have been posted a long time ago…

We started with discussion of Overdrive and how we all use it. Next up was ILS (Integrated Library System – circulation, cataloging and web OPAC, among other things) versions and many discussions of what ILS we use with lots of complaints about the vendors in the space. Travis Reddick, of MORENet, got lots of props for being a very helpful dude to work with in the networking area of MORENet. There were a lot of comments about hosted ILSs and web-based ILSs.
Next up was a discussion about tech support at the library and how far we go to help patrons as we try to do the rest of our work.

Categories
Libraries

IT security in libraries

Just as a note – I’ve been quiet because I’ve been recovering from a fairly nasty fall down my basement steps that resulted in no broken bones (yeah!) but a fair number of bruises and 14 stitches on the top of my head (boo!). I’m back in the saddle, though…

One of the biggest drawbacks to providing public access computing in a library is the fact that the public has access to the computers. I was in a web demo the other day (for the new Centurion product – we were wowed…) and the salesman asked us if we had heard of USB wireless managers. Apparently the trend to use these started in IL (at least for Centurion hearing about it) with someone putting a wireless manager coupled with a keylogger that recorded every keystroke subsequent patrons made on the computer and wirelessly sent them to the bad guy via the wireless manager. Centurion has a setting that will disable those, which is why it came up. I’d never heard of people doing this – but within a week of that demo, I’ve seen 2 stories now on similar hacks to public library computers.

The story I linked to above talks about USB keyloggers, which have been around for a while and which we have given our computers a quick once-over for at least once a day, when we are starting up the machines in the lab. This, however, includes a wireless component that means that even if we take the USB stick and confiscate it, the bad guy still gets the data, since it was sent wirelessly. This means that keeping an eye on your network logs is doubly important – any strange activity or unknown networks accessing your computers should be checked out.

Inviting the public into your network and allowing them physical access to your machines means that you have to be both aware of current trends and vigilant about keeping an eye on the computers.  I remember when the major issue we had to look out for was teenagers stealing mouse balls to use as jewelry… Now we have to make sure that patron privacy and security are not compromised just because they are using our machines!

Categories
collaboration 2.0 Libraries Web 2.0

Collaboration and Social Networking at WWD

Web Worker Daily (www.webworkerdaily.com, WWD) has been posting some great stuff about collaboration and social networking over the past few days. Here is a quick list of the best posts:

* Social Networks allow companies to call “Contingent Workforce”
* Social Tools make managing remote workers easier
* Integrating social collaboration into workflow
* Unleash employees to remain relevant

but there is much more at the WWD site, but those were posted fairly recently and all of them are applicable to any kind of collaborative work – whether you are an enterprise or non-profit organization or library!

Categories
Libraries thinking

Breaking things and making progress

One of the big “themes” in the libraryland literature (and conference programming) is failure in libraries. One of my friends, Amy Buckland, is moderating a “Failcamp” at Internet Librarian this year with Krista Godfrey, Jan Dawson and Char Booth and, though I won’t be able to attend, I do have some thoughts on the matter.
I attended the NAGW annual conference last week in St. Louis and heard Jared Spool give the opening keynote. In it, he said that “risk averse organizations produce crap” – a very twitterable statement if ever I’ve heard one – in the context of spending an hour and a half talking about a study he and his company did on organizations that produce good stuff.
Between those two themes, there are a lot of good ideas to take away. One, the fact that you have failed in a program or project does not mean that you, or your library, is a failure. Two, failure is the best way to learn. If you succeed, there is no incentive to discover the cause of the success – failure practically begs you to discover the cause and learn from it. Three, if you are afraid to fail, you will be unable to do the risky work required to truly succeed.
All of these points are applicable to everything from creating programs and events for our libraries to coding and network maintenance. I quite regularly break our Drupal installation by doing something a bit risky and I learn more about Drupal and its inner workings every time I do it. One of the major things I’ve learned is how to *very quickly* recover from a system meltdown in Drupal…
We could be scared and unwilling to try anything new and let the status quo stand, but that will never get us anything but more of the same. The definition of insanity is trying the same thing over and over and expecting different results – if we want to improve ourselves and our libraries, we have to be willing to try new things. Those new things come with the risk of failure, but, as the many articles, blog posts and conference programs show – failure isn’t the worst thing that could happen to your organization. In my opinion, not trying anything new and not innovating is.

Relation Browser
Timeline
0 Recommended Articles:
0 Recommended Articles: