Luckily I think there are some great libraries out there implementing rather than talking about the future. It does feel like there is a lot more talk than action though...
I was talking to a guy who (at the mature age of 17) says he misses the library that was, the library we people sit in obscure corners of old builds reading in absolute silence. Could it be that libraries are trying too hard?
Maybe there should be a rule: every email you send has to be accompanied by one line of code. Over a few months we could build the ultimate open-source OPAC? :)
Even better, we could invent a programming language where the syntax consists of critiques of library practices. In just a few 10,000 word diatribes we could have a complete ILS. The great thing would be that people could add new functionality to the product just by complaining about it.
Geez, Steve, only a list? Doesn't it deserve a wiki? Or, maybe, several wikis? (After all, if one wiki on a topic is good, a dozen are even better. Right?)
Web4Lib and NGC4Lib are just awash with this inane banter, and certain well read blogs on the subject (The Shifted Librarian I'm looking at you) are just as bad.
However, I can understand it being discussed on those groups, but does it really need to flow over into Code4Lib?
Can't us developers have one place where we can discuss the technical ins and outs of libraries and their systems?
Can anyone point to USEFUL research being done on real ways (with measurable results) to let users get to what they want? What are the best practices? For example: "1) Have faceted search, like this: .... 2) Show results like this... 3) Show book' physical location like this..." (wishfully thinking)
11 Comments:
I couldn't help but smile with that one :)
Luckily I think there are some great libraries out there implementing rather than talking about the future. It does feel like there is a lot more talk than action though...
I was talking to a guy who (at the mature age of 17) says he misses the library that was, the library we people sit in obscure corners of old builds reading in absolute silence. Could it be that libraries are trying too hard?
ngc4lib getting you down, tim?
>ngc4lib getting you down, tim?
Sometimes.
Maybe there should be a rule: every email you send has to be accompanied by one line of code. Over a few months we could build the ultimate open-source OPAC? :)
Even better, we could invent a programming language where the syntax consists of critiques of library practices. In just a few 10,000 word diatribes we could have a complete ILS. The great thing would be that people could add new functionality to the product just by complaining about it.
Wait a minute. I'm not so sure. Let's talk about this first. I'll start a discussion list.
Geez, Steve, only a list? Doesn't it deserve a wiki? Or, maybe, several wikis? (After all, if one wiki on a topic is good, a dozen are even better. Right?)
The truth behind it all is that libraries as we now know them have no future.
As someone who studies the history of libraries, I can accurately say that this was true about a hundred years ago, too!
How true!
Web4Lib and NGC4Lib are just awash with this inane banter, and certain well read blogs on the subject (The Shifted Librarian I'm looking at you) are just as bad.
However, I can understand it being discussed on those groups, but does it really need to flow over into Code4Lib?
Can't us developers have one place where we can discuss the technical ins and outs of libraries and their systems?
Can anyone point to USEFUL research being done on real ways (with measurable results) to let users get to what they want? What are the best practices? For example: "1) Have faceted search, like this: .... 2) Show results like this... 3) Show book' physical location like this..."
(wishfully thinking)
awesome. remembering the bigwig debate in a new light now. *grin*
Post a Comment
<< Home