Primo Implementation at the University of Kansas

Abstract

I will share mid-stream lessons learned from our implementation of Primo at the University of Kansas. In particular I will highlight (with moderate technical detail) how we: harvested data from a not-quite compliant OAI-PHM source, automated institutional holdings updates from a non-SFX link resolver, ported UI add-ons from our catalog interface to Primo (e.g., stacks maps and locations, a request link for our Aeon special collections request system), made grateful use of and modified code from EL Commons CodeShare, and reached out to our Libraries Instructional Services staff to help our Libraries staff engage with Primo and provide our implementation team with feedback.