My original idea for this blog was supposed to be what not to do and library technology disasters. So here's a post that actually has to do with that. It's about what to do to plan for a disaster.
I found an article in the Library Journal online that was written a couple of months after September 11 (a time when disaster preparedness was on a lot of peoples' minds). According to the article, for digital systems, effective protection is constructed in layers:
-The first layer is disks, and the most secure way to store data on disks is RAID (Redundant Array of Inexpensive [or Independent] Disks) RAID 1 is the lowest level of security and is simply mirroring, while RAID 5 scatters data and information across several disks, which can offer protection when multiple drives fail (though apparently it takes longer to recover data than mirroring).
-The second layer of protection actually has nothing to do with computers. It's protecting the hard disks that the data is stored on, as in installing a fire alarm or security alarm in the room that the disks are stored in. Another option is an uninterruptable power supply, which can keep disks running in a power failure.
-The third layer is to make more copies of the data, and keep those copies in a different location than the first copies (well, duh)
According to the article, Stanford University implemented a strategy called LOCKSS (Lots of Copies Keep Stuff Safe, no, seriously, that's what it stands for) which uses a number of interconnected but distant computers that share each other's data. So if one computer goes, the others have the info.
Finally, the article says that, in the event of a disaster, the best way to get a system back up and running for users is simply to direct them to a mirrored site.
Disaster preparation isn't something that anyone likes to think about, but I did think this article was interesting. I actually kind of wonder if the library I work at has any kind of system like that in place. I don't know that we'd really have to worry about redirecting users to another site, after all, if the library is closed due to a tornado or something, well, they're not going to be able to pick anything up anyway (and any and all programs would be cancelled). Though I guess they might want to know when the library is reopening, because how else will they get their free DVDs? And obviously, when the library is ready to reopen, it'll be easier to have the computers back online if everything is backed up to disk. I wonder if patron data is being backed up too? Or will the people with $150 fines just walk? What will become of our notes in their records that tell other circ people not to wave fines for that person because they're a jerk? So many questions.
Tuesday, June 12, 2007
They beat me to it!
I'm trying to think of what to do for a third post. I start thinking about regular websites... what pitfalls might be avoided there? And then I came across this page. It's got pretty much everything you shouldn't do when making a website. Guess I'll have to keep looking for a topic.
Don't: Bother With MySpace If You're Not Willing To Do A Good Job
MySpace: The hottest place for teens to hang out online. Therefore, if a public or academic library is trying to attract teens, it makes sense for them to go where the teens are, right? Many librarians have thought that way, and there are now a bunch of library MySpace pages. But do those MySpace pages really do any good? Do they really bring teens into libraries?
There was a somewhat lengthy discussion of this on Publib, a discussion list (for Public Librarians) I was monitoring for an assignment for my other class. Many of the posts were librarians asking "So, does anyone have a MySpace page? I'm thinking of doing one, do they do any good?" Most of the responses were somewhat lackluster, the consensus seemed to be "not really". But then I clicked on one of the librarian's MySpace links (one of the ones who said MySpace wan't much good) and well, it was kind of awful. I'm not going to link to it here (I'd feel kinda mean), but I will explain what I thought was wrong with it. It was just a picture of the library, with a horrific pink and flower background that hurt my eyes. There was not a lot of information, and no links to the library's website or catalog.
And then I found this awesome blog post. I'd highly recommend checking it out. The blogger, Meredith Farkas, basically sums up the usefulness of MySpace and social networking thusly:
"I have seen two ways that libraries have used MySpace and Facebook effectively. The first is to get feedback from students. The second is to create a library portal within MySpace and/or Facebook (or whatever social networking software inevitably will come next)."
Farkas mentions an academic library that used social networking to get students to request items they wanted the library to order. Which also seems like a great idea for a public library as well. It would be a place that patrons could be unafraid of leaving opinions and requests, and those would all be in one place for the librarians to look at next time they're placing an order for materials. It would also be a great way to get a look at trends, and could possibly be a way to determine programming.
There are a ton of links at the end of her post, and there is a section of "Libraries with good profiles". One of them is the Denver eVolver page, which contains a blog about teen programs and teen music and movie reviews. There is also a link to a book page where kids can write book reviews and make collection requests. There are also many links to the library website's teen section. The Hennepin County Library has a good page as well, which contains links to new DVDs and books, which is cool, because people are generally interested in what's new. Also, as much as book fans probably don't like to admit it, DVDs are a good way to bring people into the library (they're also a really good way to bring obnoxious people into the library, but that's another story...)
So in closing, of course MySpace is going to be useless if you don't take the effort to make it useful. If you're going to give it a shot in a library capacity, try to make the profile another extension of your webiste, and include links to things people might be interested in, like new books, movies, music, etc. Also, use it to give patrons a voice and a place to offer feedback.
But you know, even on the links listed above, most of the "comments" left at the page don't seem to be from library users. It looks like most of the comments left are from authors trying to push their books. So who knows? Maybe kids aren't interested in library MySpace pages. Until some library decides to release some kind of statistics like how many hits their MySpace profile gets, and whether hits on their regular webpages increased because of it, or if circulation of teen materials increased, it might just have to be one of those things you have to try and see.
There was a somewhat lengthy discussion of this on Publib, a discussion list (for Public Librarians) I was monitoring for an assignment for my other class. Many of the posts were librarians asking "So, does anyone have a MySpace page? I'm thinking of doing one, do they do any good?" Most of the responses were somewhat lackluster, the consensus seemed to be "not really". But then I clicked on one of the librarian's MySpace links (one of the ones who said MySpace wan't much good) and well, it was kind of awful. I'm not going to link to it here (I'd feel kinda mean), but I will explain what I thought was wrong with it. It was just a picture of the library, with a horrific pink and flower background that hurt my eyes. There was not a lot of information, and no links to the library's website or catalog.
And then I found this awesome blog post. I'd highly recommend checking it out. The blogger, Meredith Farkas, basically sums up the usefulness of MySpace and social networking thusly:
"I have seen two ways that libraries have used MySpace and Facebook effectively. The first is to get feedback from students. The second is to create a library portal within MySpace and/or Facebook (or whatever social networking software inevitably will come next)."
Farkas mentions an academic library that used social networking to get students to request items they wanted the library to order. Which also seems like a great idea for a public library as well. It would be a place that patrons could be unafraid of leaving opinions and requests, and those would all be in one place for the librarians to look at next time they're placing an order for materials. It would also be a great way to get a look at trends, and could possibly be a way to determine programming.
There are a ton of links at the end of her post, and there is a section of "Libraries with good profiles". One of them is the Denver eVolver page, which contains a blog about teen programs and teen music and movie reviews. There is also a link to a book page where kids can write book reviews and make collection requests. There are also many links to the library website's teen section. The Hennepin County Library has a good page as well, which contains links to new DVDs and books, which is cool, because people are generally interested in what's new. Also, as much as book fans probably don't like to admit it, DVDs are a good way to bring people into the library (they're also a really good way to bring obnoxious people into the library, but that's another story...)
So in closing, of course MySpace is going to be useless if you don't take the effort to make it useful. If you're going to give it a shot in a library capacity, try to make the profile another extension of your webiste, and include links to things people might be interested in, like new books, movies, music, etc. Also, use it to give patrons a voice and a place to offer feedback.
But you know, even on the links listed above, most of the "comments" left at the page don't seem to be from library users. It looks like most of the comments left are from authors trying to push their books. So who knows? Maybe kids aren't interested in library MySpace pages. Until some library decides to release some kind of statistics like how many hits their MySpace profile gets, and whether hits on their regular webpages increased because of it, or if circulation of teen materials increased, it might just have to be one of those things you have to try and see.
Tuesday, May 22, 2007
Newer Doesn't Always Mean Better
I found this article written by a systems librarian, who says it's not a good idea to buy the latest and greatest computer for library use (later in the article, he makes the same assertion about software and wireless options). Sure, the obvious reason is that some libraries simply won't have the money. But he lists some pretty good reasons to buy technology that is one step down from the most recent:
- Protection from new technology that, after a great deal of hype, never makes it past the first generation of products, or simply does not hold up well. He lists the OS/2 and OSI networks as examples.
- Libraries usually don't run applications that require extremely high-end performance. As long as the computer can run useful software at a decent speed, that will be enough for most libraries.
- Buying just a step down will, in most cases, provide good performance for considerably less money.
Although, he also warns that it's not worth it to buy low-end stuff, even if it is cheap, if only for its inability to run new software efficiently and possibly, waning support.
And, of course, he adds that anyone looking into purchasing technology should still assess their needs and look into all their options.
As someone who is interested in public libraries, I found this article very interesting, as well as practical. As someone who doesn't follow technology news, it never occurred to me that a hot new product could fail and never make it past the first generation. It's something to think about.
Although, the information in this article might not be as helpful to someone who is interested in specialized libraries that might require advanced technology.
- Protection from new technology that, after a great deal of hype, never makes it past the first generation of products, or simply does not hold up well. He lists the OS/2 and OSI networks as examples.
- Libraries usually don't run applications that require extremely high-end performance. As long as the computer can run useful software at a decent speed, that will be enough for most libraries.
- Buying just a step down will, in most cases, provide good performance for considerably less money.
Although, he also warns that it's not worth it to buy low-end stuff, even if it is cheap, if only for its inability to run new software efficiently and possibly, waning support.
And, of course, he adds that anyone looking into purchasing technology should still assess their needs and look into all their options.
As someone who is interested in public libraries, I found this article very interesting, as well as practical. As someone who doesn't follow technology news, it never occurred to me that a hot new product could fail and never make it past the first generation. It's something to think about.
Although, the information in this article might not be as helpful to someone who is interested in specialized libraries that might require advanced technology.
Saturday, May 19, 2007
Introduction
Hello,
This blog is for my library science 6080 class. We are supposed to discuss topics that have to do with both libraries and technology. Since I'm pretty disgruntled after the past week of trying to install software that just won't install, for my blog topic I'm going to focus on bad library technology and what not to do. So basically I'm thinking about finding examples of technology that was used in libraries and turned out horribly, (or maybe technology that was just an inconvenience). Or maybe trying to find tips to avoid inconvenience. Something like that. More to follow.
This blog is for my library science 6080 class. We are supposed to discuss topics that have to do with both libraries and technology. Since I'm pretty disgruntled after the past week of trying to install software that just won't install, for my blog topic I'm going to focus on bad library technology and what not to do. So basically I'm thinking about finding examples of technology that was used in libraries and turned out horribly, (or maybe technology that was just an inconvenience). Or maybe trying to find tips to avoid inconvenience. Something like that. More to follow.
Subscribe to:
Posts (Atom)