Stanford University have released a video demonstrating how they have integrated LOCKSS with their library catalogue and OpenURL Resolver. Like De Montfort University, Stanford use the SFX product from ExLibris to run their resolver and electronic journals A-Z list. My thanks to Adam Rusbridge of the UK LOCKSS Alliance for uploading this.
From this clip you can just about see that:
- An institution’s LOCKSS archive can be added as a target to an OpenURL Resolver;
- requests from the resolver as handled by the local LOCKSS box, working as a proxy;
- Content is served from the local LOCKSS box to the user. You can see that a local URL is displayed in the browser;
- Where LOCKSS is working as a proxy, it will still be sending requests to the publisher, which will count in the usage statistics, just as they would for any other proxy service.
This exciting preview does raise some questions:
- When are ExLibris going to release the software and knowledge base changes as an update (to SFX3)?
- Are all journals from every LOCKSS participating publisher going to bepart of the same target?
- How does SFX manage the different date ranges each object might have?
- Would it be best to activate all journals where LOCKSS holds Archival Units, or just those where (following some trigger event) access is unavailable elsewhere?
- How does LOCKSS measure traffic and manage demand for its content?
Those are my immediate questions. But this demonstration does touch upon questions of green IT. Is it greener to serve content from a local LOCKSS Box than it would be to fetch a file from the far reaches of the internet? The saving may not be a local saving, as the institution is still doing as much, if not more, work. But there should be some global reduction to the Higher Education global carbon footprint, surely?