Getting It Out of your System

At the moment I am torn between the model of a repository as a theme park (there's all the rides for you to enjoy in one place) or the repository as a DVD lending library (there's all the films there in one place, but you take them away to enjoy them on your DVD player and your iPod and your laptop and at your friend's house).

I've thought hard about this with EPrints in mind - should it offer a rich and engaging user experience there, inside the repository, with as many built-in services as possible, or should it just let you take its contents and use them in as many external places as possible?

At Southampton we build repositories (EPrints) and we build OAI services (citation analysis, open access monitoring, preservation assistance), so we're constantly asking ourselves the question "where does this go? Inside a repository or in a service?" My natural inclination is to go for the external service model - it's global and interoperable rather than parochial and platform-specific.

Put in those terms the answer seems to be a no-brainer. But the problem is that while it is getting easier to get repositories funded and supported, it is really difficult to get services funded and supported. What is the natural home for an international service? Difficult to say! If it doesn't cater to a particular institution, region or country then who is going to put their hands up and host it? Or rather who is going to put their hands in their pocket and bankroll it?

But when it comes to an institutional repository there's a different story. It has a natural home (the institution) and with it a support infrastructure and a mechanism for applying for further support to achieve new developments/updates, all because it's serving a local need. So innovations and services may perhaps emerge in the local repository, rather than in a global service.

Tim O'Reilly made a recent criticism of this approach (It's The Data Stupid) in the context of social networking, arguing that it is more important to allow users to use their information in lots of third party services than it is to make it easy for developers to create lots of applications local to a particular site.

And he may be right - the information captured by a single repository is going to be a very very small part of "the global literature". What researcher would want to be locked up with only the work authored by him/her and his/her research group, however interesting the ride!

So on the one hand external services seem to be the proper solution and on the other hand local repositories seem to be the pragmatic solution. Like I said at the beginning, I'm torn. I think that EPrints had better back both approaches!

Repository Upgrade

We switched the repository just before the weekend, so that the EPrints v3 version has now replaced the old repository. We had done all the configuration migration previously and every so often we would migrate the data contents, just to check. We suspended all new deposits and editing facilities on Wednesday, did the final data migration and changed the DNS so that eprints.ecs now points to what used to be eprints3.ecs. Having done that we left the editing & depositing locked down for a few days in case any problems became apparent. They didn't, apart from a few people reporting that the editing had stopped working :-)

So last night (Monday 12th Nov) we switched editing back on and all systems are go once again! There are a couple of niggles to sort out - the citation format isn't quite the same as it used to be (it's missing out some conference information) but apart from that it went very smoothly.

Even Less Exciting Times

I demonstrated the new repository to our research committee but it was all a bit of a letdown in the sense that they couldn't see any problems with moving to the new repository straight away. So all of a sudden the ball is back in our court, after having been waiting since the beginning of the summer.