This is a very abbreviated list that I’ll expand with a longer, more formal report, but this years code4lib left me with a few specific take-aways:
- I need to spend some more serious time considering how Linked Data projects currently being developed could impact my library. I followed peripherally the work that Ed Summers did with lcsh.info before it was taken down, but with more players (including LC) formally moving into this space, I think that the ability to build linkages to data on the web is going to get a whole lot easier.
- I want something like Brown’s Dashboard imitative at my library. The ability to track statistically information about our library services and serve it a way that it could be used by decision makers at all levels is very attractive.
- I’m going to be setting up a djatoka server when I get back to OSU. djatoka is an open source JPEG2000 server created by the folks at Los Alamos Labs that certainly looks robust and easy to use – and dove tails nicely into a project that I’m personally interested in spending more time on at OSU. Recently, OSU jointed Flickr commons and has started to release images to the collections. In Flickr, these images are seeing in a week about the same usage as we see in a year for collections in CONTENTdm. So, it makes me wonder if CONTENTdm, though a fine platform, is the most efficient way of making our image collections available – especially given that many of the archival functions could be accomplished using something like DSpace, our IR software.
- I’m still not a believer in the OLE project (and to some degree, the XC project – though that seems to have more legs to me since they are farther along). I know that I just came from an open source/project lovefest and generally we don’t criticize interesting projects but… Both of these projects are doing a lot of good work and I think will contribute a great deal of research and information regarding functionality and workflows that will help services develop into the future. However, I think that both of these projects are 3-4 years too late. I honestly believe that the ILS as we know it is dead (I know, someone should tell libraries – but its coming). I think that if OCLC every gets their act together and really makes a commitment to open the WorldCat database, then that is a game changer. But whether it’s through products like WorldCat Local, Summons, etc., I think that the idea of a localized catalog will be an antiquated concept by the time the OLE (and likely the XC) products have finally reached a level of production. I certainly could be wrong (and would be happy to be so), but the needs that these projects are looking to solve have solutions now (if just a handful of barriers preventing the free flow of data were removed).
- I’m ready to talk about something other than Solr. Yes, its cool. Yes, it is driving many of the next gen. library interfaces and is being used by libraries in lots of exciting ways – and yes, now we’ve spent a good deal of time talking about it for 3 years — let’s talk about what’s next.
- I actually left feeling a little bad for OCLC. Now, I certainly have no problem letting it be known when I think that they are acting outside of the interests of the membership. Or, letting them know that I think that their current service model for their API sucks. Or that they screwed up when they tried to modify the records transfer policy. But at the same time, we do need to give them credit where it is due. OCLC’s grid services team is doing a lot of good work trying to create a set of APIs that will finally let the membership work with data available in WorldCat. Yes, there are gaps. Yes, the current terms of service limit the API’s usefulness tremendously – but at the same time, a year ago these didn’t exist and from my conversations with OCLC, they are showing a real willingness to listen to comments as to how they can make this service useful for members. And while I doubt it will be as open as I’d like, I think that in time (and I wouldn’t be surprised if this was near time) that we will see some significant changes to the service terms to allow libraries to make use of what could be a tremendous resource. And while there was a general interest in what OCLC was doing, there was also some good natured, and not so good natured fun poked at OCLC’s expense (of which, Roy likely bore the brunt). I say, push them, prod them – disagree with them – but there have been some really impressive gains made over the last year, I don’t think that OCLC is getting credit for that. (though, if they don’t do something this year to make this API more open – well, I’ll have to take some of this back).
So those are my quick thoughts. I’ll post a more comprehensive write-up over the weekend (likely).