Name of presenter: Kasper Løvschall
About the presenter: Generalist and self-taught developer with in-depth knowledge of the “library development stack” and the functioning of the library in real world and everydaylife. Always ready to discuss topics at policylevel and help provide solutionsto actual problems.Co-awarded “The Azriel Morag Award for Innovation” with Karsten Kryger Hansen by Ex Libris and IEeLU 2015.
At Aalborg University Library as of January 2016 the subscription agent handling our paper journals could not continue to supply us with a service we had out-sourced to them.
Previously our agent provided barcode labeling for each journal issue as well as they provided us with enough information in a spreadsheet that we were able to load into our library system. Thus, each issue checked-in as arrived and available for loan. As a result, the journal issues were ready for our open shelves with very little human interaction.
This new (or the return of a rather old) situation meant that we took a move back to former tedious manual handling, barcode labeling, and check-in of each issue within the library system.Fortunately,today we are down to only 350 paper journal titles in subscription counting around 2,000 issues on a yearly basis. Nevertheless, it still takes a substantial amount of resources to perform the check-inon a weekly basis.
It forced us to rethink the task and see if was possible to optimize the workflow and limiting parts of the manual handling.
The solution was an in-house developed web application named nuKardex with the singlepurpose of performing journal check-in.This includes:
- . Locating the correct journal title and let the cataloguer select the right issue from the publishing schedule.
- Printing a label with title, issue,and shelf informationdirectly from the browser to a barcode printer.
- Checking-in the issue to the library system
- . Sending out journal issue claims. Reprinting damaged barcodes. Managing subscriptions used by nuKardex.
- nuKardexis an example of creating newand specializedapplications by using existing frame works(e.g. for building the user interface, web client interaction,and server side application programming), standard API’s and code reuse. You solve a core task by bridging the gap between interface and model.
- By using all these standard components, the development is rapidand does not as such require project management.
- This talk will focus on the above case and the idea of solving problems by making simple solutions –in this case an application with just one purpose. By focusing on a single problem, you can provide solutions that may solve the task more elegantly and faster than by using e.g. monolithic library systems.
- .nuKardex in action (currently only running a Danish user interface)–locating the journal title and location:
- Checking-in the correct issue and printing the barcode: