VuFind in 8 minutes using Amazon EC2

I’ve created a screencast showing how easy it can be to install VuFind. Here I go from nothing (no server, no OS) to full VuFind install in under 8 minutes.

It would probably take less than two minutes (under 10mins in total) to add MARC records to the installation, but I didn’t have any to hand at the time.

This demo cheats a bit by using a script that does the heavy work, the script was a mash up I created taking existing scripts and commands that come with VuFind with a few tweaks. It probably would have been only slightly slow to run most commands manually.

The script in question is at http://www.nostuff.org/vufind-install.txt and of course anyone is free to download (and improve, please share changes). There’s lot of potential to improve it’s ability to work on different flavours of Linux.

Multi Instance

One of the key aspects of the script is that is allows you to easily install multiple instances of VuFind on to a server. By default VuFind installs in to /usr/local/vufind and has other things (databases, apache conf) names vufind. The script prompts for an ‘instance name’ and then uses that in place of ‘vufind’.

The rational for this is my feeling that VuFind is an excellent tool for creating niche catalogues that are a subset of the full Library collection (or as someone put it a ‘tranche of the catalogue’). A branch Library, particular collection, rare books, a particular School, Core reading (short loan books), specialist resources (AV / laptop items for loan) etc. The idea of a organisation’s records being in system, rather than many (of varying quality) makes sense, but it’s reasonable for those moving their records to a central system to want to be able to search their records independently of other records (and expecting users to go to an Advanced search of using a refine option of the main catalogue is not really not an option). VuFind seems like an obvious answer to this. Especially if new instances can be set up quickly.

In fact it seems to be a failing of most of the main Library Manage Systems (ILS) and their web interfaces that being able to create lots of interfaces (slicing and dicing the underlying single large pool of records). Most require a large amount of effort to create a second web interface to a catalogue. This seems like such an obvious flaw and a barrier to moving to one system to manage resources such as books and other items for an entire organisation.

Amazon EC2

Amazon AWS is a great tool to use for this. A small instance will cost around $0.10 an hour, the micro instance is even cheaper (just over $0.02). Create an instance for ten hours and you have spent around a dollar. Mess it up, just destroy it and create a new one. No risk and no hassle (for first time users the hardest thing is probably the ssh private keys).

Pinboard.in suites me just just fine

About a month a go I wrote a quick rant about Delicious.com and why it could have been a sucessful web2.0 business (relatively low costs and lots of opportunity for advertising and pro/paid for features). At that time I said I was moving to pinboard.in, especially as delicious.com’s future was being questioned at the time.

This is how I use/used the two sites

  • When trying to find a site, page or link – often for a product/app/site with a name I don’t remember – I will use Pinboard’s (and used Delicious’) search feature with a keyword to try and find it, hoping that I either tagged it using the word, or title/description included it. This is my primary use case.
  • My second use case was picking a tag and browsing by it for the same reason.
  • Third use case was having no idea what I can search for, so just browsing through my entire bookmark list, perhaps picking roughly the time period I might have saved it.

I’m not looking back. I like:

  • It’s fast, clean and simple.
  • It has the features I use from Delicious and not those I was not interested in.
  • I never used the Delicious, nor can I think if a good reason to have them. Pinboard does not have them by design.
  • Automatically adding favourite tweets is a brilliant idea, I, like others, use the favourite tweet feature more as a ‘read later’ option for interesting links.
  • I use pinboard (and used delicious) as a cross browser, access anywhere, bookmarking system. No browser plugin or sync feature comes close.
  • When I searched delicious it would show three of my bookmarks and the the rest of the page would show bookmarks with the search term saved by others. This was useless to me, and just created an extra click for me to select ‘show me all bookmarks that match this search. I have one less click with pinboard which does not show me other people’s bookmarks by default.
  • I quite like the pay a little to use it concept. Even with freemium sites (which have a free option, normally the most popular, and a pro version) you are ultimately paying for both you and the cost of those using the free version. There are often anti-social users, who devalue the site and add to the cost of running it. Not so with pinboard, if you can’t be arsed to spend a few quid (or dollars) on the service then, no offense, go elsewhere. I like the fact that anyone using the site has shown a small monetary commitment to it. It makes it not another site where the whole world signs up and then forgets what it is (god knows I get enough emails a month from web2.0 services keeping me updated about their service which I have no idea what they do or why I signed up).
  • However I do find the concept of the signup cost going up with each new user somewhat strange. It might encourage early adoption but it will mean the site eventually becomes too expensive that many will choose not to sign up.
  • Likewise it’s a one off cost for a service which will have ongoing costs. So new signups will have to fund the service. Perhaps move to a $4/yr model (perhaps with multiyear discounts $10 for three years) to provide a consistent and ongoing income.

In summary pinboard keeps things simple, fast and is created by committed developers. Suites me just fine.