Join this panel as they share their experiences, research, and wisdom on discovery service implementation, from a variety of settings and with a variety of products, including Primo, Encore, and EDS. Attendees will gain a broader understanding of what to expect before, during, and after implementation and what to ask vendors to get the best information and avoid pitfalls.

1. Discovery Services
What We Wish We Had Known, or Known to Ask
Ben Miller, Assistant Director, Resources for Libraries & Lifelong Learning,
Wisconsin Department of Public Instruction
Kathy Setter, MORE Project Manager, Indianhead Federated Library System
Terri Muraski, Information Systems Librarian, Associate Professor, University
of Wisconsin-Stevens Point
Vince Mussehl, Library Services Specialist, Chippewa Valley Technical College

2. Ben Miller
Assistant Director, Resources for Libraries & Lifelong Learning, Wisconsin
Department Public Instruction, benjamin.miller@dpi.wi.gov

3. Software connects public library users to resources.

4. Discovery Layers in Wisconsin Public Libraries
● Many systems have already implemented:
○ Lakeshores, Manitowoc-Calumet - SirsiDynix Enterprise
○ OWLS, Nicolet, Milwaukee County Federated Library System, Winding Rivers, and
Indianhead - Innovative Interfaces Encore
● Additional Systems are actively planning to implement based on 2015 system plans:
○ South Central Library System
○ Wisconsin Valley Library System
● Individual libraries are also implementing Discovery Layers:
○ Fond du Lac Public library - SirsiDynix Enterprise
○ Beaver Dam Community Library - SirsiDynix Enterprise

5. Questions to ask (and why to ask them)
● How does the vendor track users and store user passwords?
○ Patron privacy.
● Can you provide examples of the metadata you provide for journal articles
included with the discovery service?
○ Metadata quality can lead to poor user experience or biased search results.
● In what way is your product interoperable with other library vendors products?
○ Who pays to connect an ILS to a Discovery Layer if purchased from competing vendors?
○ Are standards or APIs used and available?
● Who can we partner with?
○ Leverage consortia and economies of scale. Don’t reinvent the wheel!
ASK QUESTIONS!

6. Kathy Setter
MORE Project Manager, Indianhead Federated Library System, setter@ifls.lib.
wi.us

7. MORE to Discovery than you think
● 49 public libraries in MORE consortium, a service of IFLS
● Into 3rd year of a 3 year contract for Encore from Innovative
● Because of slow response time many people won’t use it, so looking for options
● Discovery layer committee formed in February 2016
● Discussed options:
○ Stay with Encore hoping response time will be fixed
○ Move to a new Discovery layer vendor
○ Forget Discovery layer and stick with just WebPac
● Looked at library websites using different vendors, highlighted likes & dislikes
● Identified products we were interested in looking at further
● Vendor Demos with BiblioCommons and Ebsco
Kathy Setter, MORE Project Manager, Indianhead Federated Library System,
setter@ifls.lib.wi.us

8. Lessons Learned:
● There is no such thing as a perfect product; nothing has everything
● Know what your top priorities are for features
○ What is essential? What can you live without, or make do with what it is?
● Ask questions; many many questions
● Be certain the product you choose has the essential features
Current Status:
● Committee recommended staying with Encore if response time issue can be
resolved; if it can’t, recommend purchasing BiblioCommons.
● This goes to the Director’s Council for discussion and vote in July
Kathy Setter, MORE Project Manager, Indianhead Federated Library System,
setter@ifls.lib.wi.us

9. Terri Muraski
Information Systems Librarian, Associate Professor, University of Wisconsin-
Stevens Point, terri.muraski@uwsp.edu

10. The UW Primo Implementation
Our Primo (Proquest/ExLibris) includes: Local Catalog, UW shared catalog, the UW libraries
digital collections and Primo Central article 10M+ article and digital repository.
2 large research institutions (Madison, Milwaukee), 11 4-yr comprehensives, UW Colleges -
separate catalogs, variety of needs
My roles (s): RFP team member, member of and later chair of the UW System implementation
team, campus project manager for UWSP.

11. Coming together & Setting Priorities
Top priorities in selection of Primo
1. Flexibility - ability to customize, use APIs, incorporate the Madison UI
2. Scope - large database, much duplication
3. Content - in the repository and the ability to add local digital collections. Ex
Libris focus on academic publishers was a plus for us
4. Infrastructure - local installation/hosted with back office/total care
Issues during Implementation
1. Beyond Local branding - agreeing on terminology, display elements
2. Speed - we harped on overall search speed and real time availability problems -
this led to a move to a move to a newer, bigger environment

12. Lessons Learned
● Agreement across institutions is worth the effort, especially if you plan central
support. Don’t overdo css changes.
● Fixing local record problems in Primo is often a choice between cataloging cleanup
or changing norm rules or both
● Vendor cooperation is essential for successful discovery
● Discovery leads to more OpenURL troubleshooting - usage of connections goes up
● Be sure to test ALL types of searching - not just known item
● Don’t just talk to the vendor - reach out to institutions/groups similar to yours who
are already using the system!
● Do as much pre-migration cleanup as possible - you won’t regret it!

13. Successes & Challenges
● Student buyin was immediate
○ Obvious starting point
○ Multidisciplinary and cross-disciplinary
● Usage has shifted beyond the Discovery service
○ Subject specific FT databases included in Primo Central is up.
○ Subject specific abstract only indexes are down
○ Non-cooperators - even with FT - are down
● We (meaning librarians) are still adjusting to the fundamental difference between
aggregator indexes (with or w/o full text) to discovery/publisher agreements.
Each renewal leads to overlap analysis.
Terri Muraski, Information Systems Librarian, Associate Professor, University of
Wisconsin-Stevens Point, terri.muraski@uwsp.edu

14. Vince Mussehl
Library Services Specialist, Chippewa Valley Technical College, vmussehl@cvtc.
edu

15. Different Roles & Different Layers
● UW-Eau Claire
○ Access Services
● UW-Stout
○ Reference/Instruction
● Chippewa Valley Technical College (current)
○ Manager/Reference/Access
Testing, Testing, Testing!

16. Discovery Layer - CVTC EDS

17. Learning Discoveries
● Learning Curve
○ No such thing as “one-size-fits-all.”
○ It’s a dog-eat-dog world.
○ Small things mean a lot.
● Challenges
○ Different vendors play the game differently.
○ Limited manpower.
○ Product customer service.
○ Technical issues.
● The Results
○ Streamlined collection development.
○ Student/patron success.
○ Library instruction improved.
○ More searches, more sessions, more full-text access.

18. For What It’s Worth
● Hand-holding is okay.
● Keep open communication.
● Bring it all back.
● Snoop around.
● Reach out to others (e.g. EDS wiki).
● It’s okay to be different. Or the same.
● Don’t plan on your go-live date.
● Ask about special accommodations.
Vince Mussehl, Library Services Specialist, Chippewa Valley Technical College,
vmussehl@cvtc.edu or library@cvtc.edu

19. Questions or comments?
Ben Miller, Assistant Director, Resources for Libraries & Lifelong Learning,
Wisconsin Department of Public Instruction
Kathy Setter, MORE Project Manager, Indianhead Federated Library System
Terri Muraski, Information Systems Librarian, Associate Professor, University
of Wisconsin-Stevens Point
Vince Mussehl, Library Services Specialist, Chippewa Valley Technical College