Behind Glass Walls

The idea of libraries moving away from being simply storehouses of knowledge, and becoming more dynamic, collaborative and allowing greater customer interaction is not new… Library 2.0 was discussed in the the LibraryJournal in 2006. While the ideas involved in Enterprise/Library 2.0 may not be new, there is one aspect which is constantly updated, and is rarely, if ever, kept up to date: technology. There are so many tools available (and foundations to build new tools); yet many libraries retain interfaces that are outdated, and do not incorporate (or worse,  hide) collaborative elements. This is an issue that requires institutions to be more nimble and adaptable, which is quite a challenge to many of the universities and city councils that run libraries.

Even if the technology is up-to-date and enticing, a more pressing issue is what the technology should allow. It is a cruel irony that many of the people that could most use the help of libraries – high school and university students, scientists and researchers and professional staff – are often the people with the least amount of time to spare to interact with the library.

For example, a few university libraries offer online chat – University of Queensland and Queensland University of Technology offer synchronous chat on their websites. I do not know how often these services are utilised, but it would seem that very few people would have the inclination to use these services. It can also be difficult to access services offered on corporate websites.

Some deeper analysis is required:

1. Which services make sense to offer? Will these services be utilised by time-poor clients?
2. How should these services be promoted? What existing services should they be associated with?
3. Are there ways to incorporate or improve other services? (It is usually better to go to where the people already are, than build something new and wait for them to come.)

Some things to think about…

When businesses are getting into Web 2.0 tools, and looking to adopt some progressive thinking, there is still “an albatross around their neck” in the form of IE6. It’s not like they can miss the fact that IE6 is hated by developers. That message has been around for years. There are so many options for browsers now:

• Mozilla’s Firefox
• Opera Software’s Opera
• Apple’s Safari
• Google’s Chrome

And word is that there will soon be another entrant: RockMelt. All these browsers are in active development, and support a much broader range of technologies. With all these options, you’d think business could find something to use? Apparently, so many businesses have web-based apps that are tied to IE6, that the reason IE6 is still floating around is because users just don’t have a choice. And there’s no solid reason to upgrade (apart from a few security issues). There’s also the issue of management – IE is by far the easiest to deploy to large installations. This begs the question – why not IE8?

This seems to go against the whole idea of implementing and incorporating Enterprise 2.0. How can modern, complex web interfaces that usually use some very advanced JavaScript and styling run on IE6, an eight (yes, count them, 8!) year old browser. In the world of tech, where applications are evolving every few months, if not faster, that seems ludicrous. However, there is not an easy solution. Any further ideas out there for how companies can at least move to IE8?