/
Library Search: Primo Implementation Update (Feb 2026)   

Library Search: Primo Implementation Update (Feb 2026)   

As we move forward with the migration of Library Search from Blacklight to Primo, we want to provide an update on our progress, clarify our approach, and outline what to expect in the coming months.  

Ex Libris released a new UI in November - Primo NDE (Next Discovery Experience), an improved interface from Primo VE, which we are currently using for Articles+. This new interface provides a cleaner, more intuitive experience focused on reducing user effort, compared to the existing Primo VE interface. Ex Libris has also made improvements to accessibility compliance and mobile responsiveness.  

Primo NDE will provide enhanced search capabilities, including the ability to search both articles and our catalog simultaneously—an "everything" search we don't currently offer. We will also be adding a browse search to enable users to browse by title, author, subject, and call number. Overall, we expect the improvements to make research more efficient for our users.  

Where We Are: Project Timeline  

  • January 2026: Moved from planning into active implementation phase  

  • Late Spring 2026: Beta launch for community testing and feedback  

  • August 2026: Target date for production launch  

Project Structure: Who's Leading This Work  

Our implementation is guided by a focused governance structure:  

  • Library Search Steering Committee (LSSC): Serves as the decision-making body, balancing competing interests and establishing overall direction. This committee includes library administrators and members from Technology and Digital Strategies.  

  • Library Search NDE Implementation Task Force: Led by the Discovery and Delivery Program Manager, this deliberately small, agile team provides recommendations to the LSSC. Members bring expertise in cataloging and metadata, e-resources management, user needs across all levels, instruction, and Alma/Primo configuration.  

While the core team is intentionally compact to maintain agility, there will be ample opportunities for soliciting guidance from subject matter experts across the libraries throughout the project.  

Understanding Our "Minimum Viable Product" (MVP) Approach  

One of the most important aspects of this implementation is understanding what we mean by MVP. MVP does not mean "unfinished" or "incomplete"—it means "fit for purpose."  Think of it this way: We're building a house that's "move-in ready" on Day One. The foundation is solid, the roof is secure, the plumbing works, and the locks are safe. Our users can "move in" and conduct their research effectively from launch. After we're live, we'll continue to "decorate and renovate"—adding enhancements, optimizing features, and responding to evolving needs.  

 

What's Guaranteed in Our MVP (Day One Functionality):  

On launch day, Primo NDE will enable users to:  

  • Discover our collections effectively  

  • Access our collections (with proper authentication) 

  • Request our collections (ILL, Course Reserves, Special Collections)  

 

Core capabilities include:  

  • Robust search functionality (single-box, advanced, journal, browse)  

  • Working facets and filters  

  • Full-text resolution ("View It" links)  

  • Integration with ILLiad, Ares, and Aeon 

  • Emory branding and responsive design  

  • Citation export tools  

  • Analytics for usage tracking  

  • Integration with LibGuides, Article Galaxy Scholar, and Third Iron 

 

Our Strategic Approach: Configuration Over Customization  

Following leadership guidance, we're prioritizing out-of-the-box vendor functionality and strictly limiting custom code. This "configuration over customization" strategy ensures:  

  • Long-term system stability  

  • Easier maintenance and updates  

  • Ability to take advantage of new vendor features as they're released  

  • Reduced technical debt  

 

What Comes After Launch?  

Launch is not the finish line—it's the starting line. Primo NDE is a dynamic platform that will require ongoing care and iterative improvement. Features determined to be out of scope for our MVP release (such as experimental AI features, deep customizations, and vendor roadmap items) will be classified as enhancements. These will be prioritized and implemented in line with our regular enhancement schedule after the system is live and stable.   

What You Can Do:  

  • Stay informed: Watch for updates as we approach the beta launch  

  • Plan to participate: We'll need testers and feedback both before and after our beta launch  

  • Share your expertise: Subject matter experts will be consulted on specific aspects throughout implementation  

Questions?  

The Implementation Task Force and Steering Committee are committed to transparency throughout this process. If you have questions or concerns, please reach out to our feedback team at PrimoNDEFeedback@emory.edu.

Thank you for your patience and collaboration as we work to enhance Library Search for our community.