As regular readers will know, we have been working with repositories for quite a few years now. In 2005 we began working with the School of Advanced Study on their requirements for an Institutional Repository, and since then we have installed, configured and maintained several repositories, including some highly customised, specialist systems.
In most cases we have used EPrints. This is partly because we are familiar with the stuff it is built with (Perl, MySQL and XML have been at the heart of the NDAD dataset repository we have operated for The National Archives since 1997). But also because we like the ever-expanding set of features and options EPrints provides. I’ve watched its capabilities grow, thanks to the seemingly limitless energy and initiative of the EPrints team at Southampton. (For an interesting, user’s-eye perspective on the relative merits of DSpace and EPrints, I recommend reading some of the posts tagged DSpace in Dorothea Salo’s Caveat Lector blog).
It’s three years almost to the day since Rory and I attended the pre-launch briefing on EPrints3 and came away convinced that, with its AJAX UI and evolving plugin architecture, EPrints 3 was likely to play a big part in our future plans.
And hardly a day’s gone by since, when we haven’t had some EPrints-related work on our plate. In 2007 we began developing Linnean Online for the Linnean Society, and PRIMO for the Institute of Musical Research. Out of this, and the snowballing Web 2.0 zeitgeist, we also honed the idea that became SNEEP (Social Networking Extensions for EPrints), one of the first JISC Rapid Innovation projects. Most recently, we’ve scaled new heights of EPrints customisation with the SOAS Fürer-Haimendorf collection, with its user-defined albums and searching enhancements, all wrapped up in 9Web’s impressive graphic design.
We’ve tweaked config files and hacked templates and for the most part enjoyed doing stuff with EPrints. (All credit is due to Rory and Ben, by the way. My role is chiefly to say “We could make it do that couldn’t we?” And, lo and behold, usually “we” can.)
Over the years I’ve also talked to many repository managers, and potential repository managers, about their requirements and expectations. I’ve spoken and networked at DSpace User Groups , Open Repositories conferences and many excellent events organised by the JISC, particularly the Repositories Support Project – and I’ve met a lot of smart and insightful people in the repo biz. Some of it must have rubbed off – I think my own understanding of what’s needed, and what’s feasible has grown considerably.
But what we’ve never done is run our own repository, and experienced these things day-to-day for ourselves. As Atticus Finch said in To Kill A Mockingbird,
You never really understand a person until you consider things from his point of view . . . until you climb into his skin and walk around in it.
That’s why, in the gaps between everything else going on round here, Annemarie has been putting together the ULCC Publications Archive, which I hope will become a canonical home for our published outputs. It’s not big and it’s not clever, it’s certainly not perfect, but it is something we can use to improve our understanding of what it means to run a repository. We will also no doubt use it to explore some of the tools and techniques emanating from the EPrints developer community.
And now I can really start to empathise with the repository managers I know: their agony – clarifying copyright and licenses, ambiguous form fields, disappearing diacritics – and their ecstasy – a well-formed subject tree or citation, a successful search. I’ve also an insight into the needs of authors/submitters, since several articles are mine – and I naturally want to get the citations looking just right, so that I can embed some of the nice feeds EPrints provides into my blogs, e-portfolios and who knows what other mashups. Self-interest is a great motivator, as many Open Access advocates have observed: before long I’m sure I’ll be wanting download statistics, author profiles, and most of the other things I described in 1001 Things To Do With A Live Repository.
For me it’s an invaluable experience – no less so than when, a couple of years ago, I became an actual user of a VLE, through my MSc course at Edinburgh. There’s a world of difference between being a developer or implementer of this kind of online system – thinking your job’s done when it seems to be up-and-running – and being the poor end-user who doesn’t care about PHP, JSP, Maven, Apache, etc, but just wants to get something done.
Among the things you’ll find in pubs.ulcc.ac.uk are: papers and articles from events we have contributed to over the years, such as iPRES, Open Repositories, and DLM-Forum; published reports, like last year’s JISC-PoWR web preservation report; presentations and posters from other events, mostly in the field of e-learning or digital archives; and even the swish product sheets produced by our ace marketing department, Tim and Frank!
As well as our most recent UK activities, we’ve also unearthed some other curios, such as Patricia’s article for the Catalan Archivists’ Forum, in Catalan, and a piece by Kevin in La Vanguardia, in Spanish. Also of interest is a brief account of ULCC’s first 30 years, in the form of a brochure for a small exhibition that was held at Senate House Library in 1999.
No doubt as we delve through our own digital archives we’ll find more goodies. Having a repository is an excellent opportunity to locate and appraise these things, and share those that seem interesting and informative enough. No less than this blog, and our E-learning colleagues’ El Blog, it should be an attractive and effective shop-window – just like any good Institutional Repository.
