What I Learned Today…

Web 2.0 and programming tips from a library technology enthusiast, What I Learned Today… covers blogs, rss, wikis and more as they relate to libraries.

State of our ILS

May 4th, 2006

This was posted on our Intranet by our head of Technical Services:

This year during the ILUG @ AALL (July 2006). There will be discussion on the State of the Innovative System. I would like to get your thoughts and present them during this discussion. Things that will be discussed are:

How has Millennium worked in your institution? What has it helped? What problems has it raised? Where does the Innovative system fit into the IT environment of your institution? … From the standpoint of you and your institution, where do you see library system software heading? Are there any implications for the overall business model?

So I of course had to answer – and since it was such a long answer and the kind of thing I’d usually post here I have decided to share my answer with you all.


First I’d like to state that I can only speak from the point of view as a programmer and web designer -I have no idea how this package works for the people at circulation, cataloging or acquisitions.

How has it worked? This is a question for the people I mentioned above. How has it adapted to the times? This is a better question for me – and the answer is poorly. The interface is clunky at best and the customizability requires more work that it’s worth. There is poor HTML and CSS hidden from the people who can make a difference. A year ago there was an extra tag – I had to wait for a new release to fix this problem when I could have easily gone in and deleted it if I had the control. I frequently have to tell people in my workplace that I can’t change or fix something because it is out of my realm – nothing should be out of my realm – we pay for this product and should be able to alter anything and everything we choose.

What has it helped? Once again I don’t think this really applies to someone in my position.

What problems has it raised? It has raised several design issues – with more open code, or an API I’d be able to go in and make things look the way we’d like – instead of having to explain to people that the catalog design has nothing to do with me – the web designer. It has also caused issues with the way we store data. We have a separate customer database and we have to import data into the III on a nightly basis – if we were allowed to run simple “select” queries and edit the coding behind the scenes, we could have access to more up to the second data by pulling it directly from our database. The same goes for information we’d like to get out of the system. The statistics provided to us are spotty at best, there are missing pieces that, given the rights, we could be getting for ourselves out of the database.

Where does III fit? I’d say it’s a like the crazy cousin you have to deal with because he’s family! It doesn’t fit, we are a very open IT environment, we have applications all over that need to talk to each other nicely and the III system is a brick wall preventing us from getting the information we need and sending the information we’d like.

Where do I see it heading? No where – I haven’t seen any changes that have been advantageous to my work or my department. Where would I like to see it headed? I’d like III to look at Talis (http://www.talis.com/home/), I’d like them to see how this company is communicating with it’s users on the user level. I want to see III join forces with Talis and the other vendors to implement the idea of the Platform (http://www.talis.com/platform/) by visiting the Shared Innovation site (http://www.talis.com/tdn/) and working together. We pay for these applications and should have the ability to model them around our own business model and company mission.

I’m not sure I understand the last question – but I read it like this, “What’s wrong with the current business model and how can we change it?” Right now libraries are required to buy the same main package and then have the option to add on additional features/packages. A quote from my blog:

“Library 2.0 is about opening the library up and delivering content to our users where they are when they want it. We need to engage our users – which we are doing, but we need to do even more. Paul called for us to “disaggregate our monolithic library systems”. He explained this to us like this: Imagine a great big black box which a vendor sells you and instead of taking everything the vendor offers you take only the bits you need. Plugging in bits of other applications – maybe from other vendors – or that you have written yourself. Which is what I have the hardest time with – we have this ILS that was written for primarily academic libraries and we’re forced to buy the whole package and use only 1/3 of this – then out comes an add on that makes more sense for us – but we have to pay extra to get it – why not let us pay for the core and then pick and choose the other pieces we’ll need – customizing our catalogs to our specific institution? Paul says library systems should be like Lego, you can build the picture on the box or you can build something new and different.” (http://www.web2learning.net/archives/266)

Let us make our own packages – why should we be paying for a user database when we already have one – why not let us write a bridge script to get the information to and from our database instead of having to rely on the limits imposed by the current system?

It’s a new world and building onto a system that is more than 15 years old isn’t going to cut it anymore – there needs to be a new system, one that allows for more freedom, and it has to come soon, because more and more libraries are going to turn to open-source. I know that I’m ready to go out and lend a hand on one of the open-source LIS projects out there – especially if it means I get to have a system that will do what I want, how I want – and let me make changes when I want.

Additional Reading:

Learn all about our Intranet

May 3rd, 2006
ONLINE Magazine Cover
Cover from Official Site

It’s finally here! After talking up our Intranet here on my site (here, here, here, and here) and whenever I talked to people in person, the article is finally here.

My assistant (RayAna Park) and I were lucky enough to get the cover of this month’s issue of ONLINE Magazine and we’re so excited! I was thinking I might share snippets of code with you all throughout the year, so let me know what pieces you want more information about. I’ll admit that we did not write the object-oriented code (like John recommends) but it could still be helpful and useful for you and your library.

Lastly, if you want to learn more you can come see me at the LITA National Forum in October or Internet Librarian (also in October) I will be presenting at both conferences about our Intranet and it’s its uses.

[update 8/30/06] It has been more than 90 days so I am allowed to put the full text of the article online. Read it here. [/update]

 

 

 

The NextGen Librarian’s Survival Guide

May 1st, 2006

Okay, this is not a complete review because I’m only on page 70 out of almost 200, but I wanted to let you all know that I have started my copy of The NextGen Librarian’s Survival Guide and I’m loving it!

Having worked in a library for 5 years (as of next month) some of this is review for me – but I can remember being fresh out of college and feeling some of the same things as Rachel’s survey respondents – in fact I still feel them sometimes. I liked the idea that a NextGen Librarian is not necessarily a 20-something librarian, a NextGen Librarian can be anyone just coming out of school with their MLS. While I understand this in theory, it’s not always true. It seems that a lot of the quotes Rachel uses are from younger librarians dealing with these issues. The way I see it (and this is a generalization – not necessarily true in all places) if you’re a 50-something recent grad you’re going to get more respect than the 20-something recent grad – solely because of your age and the fact that you’ve (most likely) had professional experience before this.

Anyway, I got a little off topic there.

So far I’ve read about library school and the job hunt. I was grateful for the chapter on library school since I am currently undergoing the application process. There were useful links to scholarship information and mailing lists like NEWLIB-L and NEXGENLIB-L (which by the way was a real pain to sign up for – Topica bombards you with 20 or 30 offers and it takes a lot of clicking “skip” to get signed up). There was also a tip that I had gotten from Marydee at CIL this year – take classes you might not think you’ll need. It will not only pad your skill set on your resume, but you’ll learn something new and that is always useful.

As for the job hunt, there is a wealth of information for those of you in that position. One that makes the most sense is to take part-time positions in the field if that’s all you can find and work another job to make up the funds you may need – this way you are adding experience to your resume and learning the ropes – even if it’s not your dream job. I was lucky lucky lucky when I graduated. I got a great full-time job in a library right out of school – and at that time I didn’t even know that this was what I wanted to do for the rest of my life – I just figured it was a job and I’d move on in 3-5 years. Now here I am applying to graduate school so I can become and “official” librarian.

That brings me to another annoying point – this snobbery about “You’re not a real librarian”. This was mentioned in the chapter on Surviving Entry-Level Positions – and it’s so frustrating. I’m all for education – and continuing education specifically – but I don’t think a degree makes you a real anything. Experience and love of the field make you a real librarian – not that simple piece of paper you got 30 years ago – because we all know that what you learned 30 years ago is nothing like what you’re doing today.

Rant over.

Anyway, my initial review is that this a worthwhile read and I’m going to be writing up a book report to share with everyone here at work once I’m through reading.