johns smith-3
TRANSCRIPT
Integration or Bust –Making a Migration Work
Susan Johns-Smith
Systems Librarian / University Professor
Coordinator of Library Systems Consortia
Basic Integration Projects
• Integration for Discovery Data
• Integration of API Functionality
• Integration of Patron Data for Identity Management
Local Data : Pittsburg State• Southeast Corner of Kansas
• 7,000 FTE with faculty/students living in Kansas, Missouri, Oklahoma, and Arkansas
• Multi-type Consortia: K-12 school district, 4 public libraries, 1 community college
• Subscription to Summon Discovery Platform since 2010
• ILS Migration from Dynix / Horizon > Sierra / Encore completed fall 2014
• 1.2 million items; 850,000 bibs; 65,000 patrons
Discovery Integration (2010)
• Discoverability of the MARC data in Summon closely mapped to MARC data from online catalog
• MARC data synchronized by FTP daily for additions, changes, and deletions using the MARC history file
• Availability of book /online catalog material displayed with a “click” (URL redirect) to the public catalog
Discovery Integration (2014)
• Whoops! No history file!
• Workflow : suppress – output – review – discard
• Additions, changes, deletions output daily
• Full database refresh – quarterly or per semester
• Upload to Summon from Sierra via FTP
• SQL scripts at a future time
Sierra/Encore Integration (2014)
• Sierra updates go to Encore automatically
• APIs (Patron Loads; Fines &Fees; Backup)
• More concise integration projects included Syndetics cover art/content ; Debt Collection (Unique Management), z39.50 for record loading
• User Authentication for Patron Empowerment
Basic Integration Strategies
• Drop in a Key – Start your engine, and go!
• Profile Setup
• APIs
• Identity Management and Authentication Processes
• Discovery Integration
• Karma / Magic / Serendipity
Profile Setup
• Profile screens populated with multiple options
• Some repetitiveness if multiple profiles required
• Still fairly successful, but does require testing
• Can be additional $$ depending on product and vendor
• Is license per library or per server?
• Does it work with multiple accounts?
APIs
• APIs are “the way forward”
• Must understand local programming skills needed
• Must know data mapping and terminology of the vendor fields
• MOU or service level agreements
• Unique local coding benefits > user communities
Identity Management
• What will the patron use : SIP2/NCIP – LDAP - Active Directory - barcode & pin - Geolocation IP?
• What will the staff use : Standalone login/password –LDAP - Active Directory
• What to do for multiple sources of authentication in different identity environments – no barcodes, different campuses?
Acknowledgments
Claymore2211, https://www.flickr.com/photos/94105490@N04/1137563116/ via http://compfight.com, https://creativecommons.org/licenses/by-nc-nd/2.0/
Universal Pops (David), https://www.flickr.com/photos/43164076@N06/5593449594/ via http://compfight.com, https://creativecommons.org/licenses/by-nc-sa/2.0/
Wayne Stadler Photography, https://www.flickr.com/photos/38658617@N00/17130630715/ via http://compfight.com. https://creativecommons.org/licenses/by-nc-nd/2.0/
Jessica Shoupe, https://www.flickr.com/photos/83952735@N00/26282201526/ via http://compfight.com, https://creativecommons.org/licenses/by/2.0/
Dennis Purdy, How many times, http://www.memes.com/img/400089
MarnieJoyce, https://www.flickr.com/photos/54205314@N02/5076743386/ via http://compfight.com, https://creativecommons.org/licenses/by/2.0/