About BLMS

KDUK returns – 19th June 2014:

Student, Research Management, Finance (and a touch of library)


Following the hugely successful 2013 KDUK, Kuali returns to Bloomsbury to show more of the potential for the UK HE sector. Keeping your money in your service is a major selling point – offering greater flexibility to adjust to changes in demands in a way that is just not possible with vendor driven systems.

2013′s KDUK focused on OLE – the Open Library Environment.

2014′s KDUK is the year of Kuali enterprise systems, which are all operational and delivering the promised benefits.

The US Kuali community is extremely active and supportive, welcoming other partners whatever their location – including South Africa and the UK.

Coventry University have led on bringing the wider Kuali suite to KDUK 2014, collaborating with the Kuali Foundation, JISC and SOAS to do so.

SOAS is the UK and European lead on implementing OLE and has been working engaged with the OLE community since November 2012. In terms of Kuali’s wider potential, OLE is underpinned by the Rice middleware and Kuali Finance – which is the most mature of the complete suite.

 About BLMS and OLE at SOAS

The traditional LMS model in which most functions are managed within the Library on a suite of locally-controlled systems is being challenged by new initiatives such as shared bibliographic data (e.g. OCLC WorldCat, shared resource discovery systems (e.g. Primo Central, Zetoc, Jisc Discovery), union catalogues (e.g. Copac, SUNCAT), federated catalogues (e.g. Archives Hub), shared resource-management (e.g. Knowledge Base +). What is the scope of a 21stC LMS? How much must remain locally-controlled, how much can be shared, how much can simply be accessed from other online systems?

Sharing in this sense goes beyond the hosting and support of the systems, leading to increased opportunities for interoperability between libraries in an environment where there is already a high-level of interaction e.g. through inter-library loans, visitor schemes and extended borrowing rights, in many cases mediated by national and local agreements such as SCONUL Access, RLUK, University of London, M25 consortium. Significant sharing of materials is also becoming a major factor, through initiatives such as EthOS (for theses), the UKRR (for serials) and (potentially) a Research Reserve for monographs.

Against this background of technological and organisational change, the Libraries of the five Bloomsbury Colleges and Senate House Libraries  formed a consortium in 2012 to investigate the feasibility of operating LMS as a shared-service.

This major project followed a vision to deliver a new set of services based on open source systems i.e. Kuali Open Library Environment with a VuFind Discovery top layer. The service model will be expandable and extensible to other partners.

OLE has been developed by SOAS as the lead institution, and is currently in testing, ready for a phased rollout during 2014/15.

VuFind has been in operation at Birkbeck since 2012, is in testing at SOAS and is live at Senate House. Users have welcomed the friendliness and ease of the interface, whilst libraries have welcomed the speed and ease of developing it to suit needs.

The first Kuali Days event for the United Kingdom – 2013

Led and organised by the BLMS partners with contributions from EBSCO and K-Int, the Kuali Foundation held a Kuali Days Event in October 2013 at Senate House in central London. You can see the schedule for the event here: http://www.blms.ac.uk/kuali-days-uk-summary-of-schedule/.

Follow this link to the page which includes slides and recordings.

More information

If you would like more information, please contact

Sharon Penfold
BLMS Project Manager
c/o SOAS Library, C17
Tel: 020 7898 4797
Mobile: 07921 311179
e-mail: blms@soas.ac.uk

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>