The focus of this sprint has been migration. Ten are now the customers migrated to the KeyLinks system, but we haven’t forgotten about integration either.
This sprint, we’ve been focused on migrating rebus:list users onto KeyLinks. We’re happy to say that 10 customers are now officially KeyLinks users, with 8 of them live.
It’s important to everyone that the transition from rebus:list to KeyLinks goes smoothly. Luckily, we have an excellent group of users who are happy to communicate with us and keen to participate in the process. Their feedback, highlighting of issues, and time spent testing all areas of the system have been critical to the KeyLinks development process. In preparation for the migration, the userbase has engaged in some intense testing, looking at data, functionality, infrastructure, and potential enhancements. When customers provide feedback for enhancements, we take these into review in order to consider how they can best be planned in for future development.
Although this sprint has mainly prioritised migrations, we have also completed additional work on the Digital Content Store (DCS) integration. In particular, we wanted KeyLinks to send the data entered in the Request Digitisation Form into the DCS Course Content URL API. In this way, the DCS can record it for a librarian to put into action later. Ongoing work to integrate KeyLinks and other systems will better connect library and academic teams within institutions. As well as this, we are working on saving time and making resource list creation and management simpler.
We will be working on continuing to finalise the last of the migrations while also ensuring that the system and customer are ready for KeyLinks first academic year of use. As always, you can expect a blog post detailing the results of our next sprint right here on the KeyLinks website, or you can contact us directly with any questions or to request to be added to our newsletter mailing list.