Core Competencies for Librarians — with all the stapling-jello-to-the-wall goodness of the Information Literacy Competency Standards (which are identified as a core competency, no less)! Get yours today! (Consult your physician before ingesting). According to Library Journal these were approved yesterday.
It has been over a year since this report came out, but it is worth mentioning again: ‘Google Generation’ is a myth, says new research. In other news, not all men good with socket wrenches and some white men can jump (see under: Bird). Can we stop informing policy and curriculum decisions with intergenerational stereotypes now?
Over the last couple of days there have been a few interesting posts on the cloud and interoperability. In a usenet post from the Cloud Computing Interoperability Forum (CCIF) Rueven Cohen notes that
Every new cloud service provider puts there own spin on how a user or cloud application interacts with “their cloud”.
The problem I see is each cloud appears be a silo upon itself. By each new cloud providing their own new API, which effectively means that your only real option is to go with the largest player, not the best. API propagation is killing the cloud ecosystem by limiting cloud choice and portability. In order to use Amazon, I am being forced to choose their way of cloud interaction / control over any others including the ability to use my existing data center resources seamlessly. (emphasis added) [source: http://groups.google.com/group/cloudforum/browse_thread/thread/3f8ee602f6617a18]
This highlights several of the issues that should be worrying academic libraries.
The content that users will want to store in a cloud system will be a hybrid of their own content to which they own the rights and content from licensed sources where the right to make copies is limited by the license agreement that the library has signed — i.e. journal articles and ebooks.
Many of the users of cloud systems will only be members of a university community for a short, pre-defined period, ie. 4 years. If the library builds its own cloud (to accommodate license agreements), how does the user move their data when they move on from the University. Or, if the University relies on other people’s cloud services, how do they deal with the fact that users will be taking licensed material and storing it on unauthorized servers and sharing it with unauthorized persons?
How does a library construct their services to allow a user to work with their choice of could services in the most seamless way? Users shouldn’t have to save an article to a hard drive when the goal is to save it to their own cloud-based service. Will APIs be written to allow such integration of services? There are already a myriad of library-provided online resources that don’t play well with anyone, never mind a user-defined choice of cloud service. Can this be overcome? Will information resources continue to be imprisoned in this way?
No one wants to commit their valuable data to a service where they won’t be able to change their mind later. I may use Google Docs today but later decide to switch to iWork. It is a reasonable expectation that I should be able to move all of my information easily, without loss and without complication. The mere suspicion that I’ll be locked in can be enough to reduce uptake.
Cloud computing has been pushing its way into my consciousness again this week. It reached the point of indigestion with Michael Stephens name dropping the computing meme of 2008 in his “Ten Trends and Technologies of 2009” but the cloud really pushed its way into my consciousness with the introduction of iWork at the Apple Keynote Adress earlier this month.
Lets get the big one out in the open early. Copyright. For those who sneer at the use of the phrase “fair use,” the era of cloud computing is going to be your own personal hell. Cloud computing is built around the idea of shared documents and files. Enforcing copyright in the era of the cloud is going to be a nightmare. Freely collaborating with a community to develop and distribute an idea, however, will become easier than ever.
Services like Google Apps, Zoho, iWork and others allow multiple parties to access and share files without purchasing expensive suites of applications. On the surface it looks like a wonderful brave new world, but are we heading for another instance of format wars?
In his review of iWork Liam Cassidy says:
And here’s the really clever part that everyone who has ever collaborated in an online workspace will love: the ability to automatically make the document available for your Viewer’s to download in all the most common file formats.
Formats. Remember when MSWord couldn’t read a Word Perfect file? When Macs and PCs couldn’t exchange data (easily)? Formats became the poster child for open computing. Programs that didn’t support the right formats became relics and disappeared. But these common file formats refer to traditional desktop computing formats — .doc, .pdf, etc. This is important if you are downloading the file to edit in MSWord, but with cloud computing format should be irrelevant. It will be access that determines the relevance of the service and the extent of the collaboration.
If I write a document in a service such as iWork I can share it with anyone, but if they want to contribute to it they will need to sign up for an account. The Mac vs. PC religious wars could begin to look childish as people wonder why they cannot directly open the iWork document their client created in their Google Docs account. After all, it’s just a .doc file which both can read, why isn’t there a way to take the document that my friend created in Zoho and open it in Google Docs without needing to download it to my computer first? Tribes will form around services as people begin to resent the idea of signing up for accounts — especially paid accounts — or downloading anything to their computers. I fear the cloud because I fear the day someone gets snobby about which service I’ve signed up for. I also fear the day that “the kids” don’t know how to manage local files and can’t ship from one service to the other. Damn kids.
Wan, Z., Y. Wang, and N. Haggerty. “Why People Benefit from e-Learning Differently: The Effects of Psychological Processes on e-Learning Outcomes.” Information & Management 45.8 (2008): 513-21 [UTL]
The article reports the results of a study into the psychological processes related to successful learning in an e-learning program. The study uses social cognitive theory. The investigators considered three types of information communication technologies (ICT) — information seeking, computer mediated communication and online socialization — influenced “virtual competence,” and how virtual competence in turn affected both success and satisfaction with e-learning.
Virtual competence has three dimensions:
It is interesting that the data did not establish a connection between experience with ICT and e-learning outcomes. They did, however, establish a connection between high virtual competence — especially the information seeking and computer mediated communication skills — and successful e-learning outcomes.
Their basic recommendation is that pretests be developed to help users assess their own levels and choose the appropriate method of instruction.
This is kind of experimental. I’m just going to start linking to interesting articles that I find. I’ll try to provide two links. Clicking on the title will bring you to the publisher’s page. Clicking on [UTL] at the end will link to the University of Toronto’s online collections. You’ll need a password for these.
The basic tools that I use every day are
Basically, I read material using the browser or skim. If something — an entire document or just a passage — it gets copied into Devonthink for later. If it is really useful its citation information gets added to my bibdesk bibliography. All writing is done in Textmate because it integrates so well with Bibdesk. Because various bookmarklets, OSX services and other trickery allow me move data between the applications with a click of a mouse or a keyboard shortcut it feels as though these five tools behave as a single application. Perhaps one day I’ll get around to compiling a video of what this looks like in practice.
Sean Devine has written a piece about the iPhone app store in which he notes that,
The KEY to maximizing iPhone profit is to create very high switching costs for users, just as they did for the iPod via the iTunes Music Store. Apple is using the App Store to create switching costs, and they know that if all of their users have “invested” in many little applications that will only work on the iPhone (a la songs from the iTunes Music Store), they will eventually have users locked in to a long-term investment in the iPhone franchise. [source: Deal Range]
I think he’s on to something here, but I’m not talking about the app store. I’ve recently had an experience where a non-monetary cost of switching caused me to continue using an slightly inferior product.
In mid-December I started playing around the with Opera 10 alpha and the WebKit nightly builds. Incredibly nerdy for someone not in web design but these things interest me. Both browsers are able to render a page incredibly quickly — faster than the current version of Safari that I use. Opera, however, really caught my attention and the more I played with it the more I found it becoming my primary browser.
During my two week winter vacation I found myself using Opera for just about everything and figured that I had once again found myself listed as an Opera convert. Until I had to go back to work. On that fateful Monday morning I plugged in my iPod to sync up all of my important data and suddenly realized that by using Opera I would no longer be able to have my bookmarks updated on my iPod.
I hadn’t been doing much mobile browsing while on vacation so I hadn’t noticed that the bookmarks were out of date. I don’t even use bookmarks very much but this was enough to make me think twice about my little dalliance with a third-party browser. Despite all that I gained by using Opera, the threat of having to type in URLs in mobile Safari was enough to bring my back into Apple’s sandbox.
I’m still wavering on this decision. This isn’t about a purchase making the cost of switching too high (as in Devine’s piece), but about a fairly trivial piece of functionality driving up the cost of switching. I really do need to let myself be comfortable with the fact that Opera is the better browser.
One of my favourite tricks for teaching students how to search the library catalogue is to prepare a list of common subject headings to help students begin navigating through a topic. The subject headings that I use are closely mapped to their essay topics so it is easy to raise the relevance of the session while also having a constructive conversation about headings in a discipline are constructed and how well these subject headings work for a given topic. Here is an example from a recent Canadian Politics class (the essay questions are not included. The student did have to do some intellectual work to figure out which headings went with which of the 50. In some cases an essay topic might require a student to use multiple headings, thus helping them to better understand the scope of their research)
The old catalogue interface supported this quite nicely. The result of a subject search was a list of subject headings that you could browse through. In the new interface the result of a subject search is a list of titles that contain the searched terms in their subject fields. One must click through the detailed record to see exactly what these headings are. There is no ability to browse the headings.
The new interface makes teaching subject searching more difficult because it lacks a browsing feature. I have to fall back on the techniques that I use for teaching subject searching in journal indexes but the two systems are not the same. Indexes usually have abstracts which tends to make them more forgiving when it comes to term selection. The catalogue lacks this nicety.
The new library catalogue interface brings a lot of nice features to the table but the loss of the ability to browse through subject heading hierarchies is a disappointment. I'm trying to figure out a way to use the subject facets to fulfill the same purpose but for now I am not sure that the impact will be the same. Being able to browse the headings allowed people to explore categories of information without being distracted by title lists. There was something powerful in being able to show students that knowledge could be organized and that the system of organization could help them build their understanding of the topic. I'm still not sure how I'm going to fill the void that's been left in my meagre repertoire.