TRLN Discovery

TRLN Discovery is a collaborative software development project to implement a modern and open-source discovery service which allows the user to conveniently find and access materials from all TRLN member libraries within a single search environment. It is unique in uniting the catalogs of multiple independent institutions who are not part of the same system. Learn more about the project below. Questions or requests for more detail may be directed to info@trln.org.

About TRLN Discovery Infrastructure

TRLN Discovery serves thousands of users from Duke University, North Carolina Central University, North Carolina State University, and University of North Carolina at Chapel Hill. The project was built using open source software tools and can be locally customized. The consortium wide index is based on a SolrCloud cluster hosted in the Amazon Web Services (AWS) cloud. Each institution hosts a customized Blacklight discovery interface, but is based off a centralized Rails Engine.

Related Presentations

Recent News for TRLN Discovery

[heels_list_posts posts=”3″ category=”TRLN Discovery”]

Project History

In late March 2016, TRLN announced its decision to replace the existing Endeca-powered library catalogs and Search TRLN with a new discovery service aligned more closely with TRLN’s current context. This decision was reached in part due to Oracle’s cessation of development of the version of Endeca used for Search TRLN. While Oracle encouraged TRLN to implement the new version of Endeca set to launch in Spring 2016, they clarified that the effort involved in installing and implementing a new version of Endeca would equal or surpass the effort invested in developing Search TRLN initially.

Through conversations with various TRLN councils and committees, TRLN decided to pursue the implementation of a new discovery platform, with Blacklight and VuFind identified as high-level candidates. Two groups were formed to lead the development of this project — an Advisory Team with membership representing the Technology Council, Services Council, and Collections Council, to oversee the project timeline and goals and liaise with campus stakeholders on major decisions, and a TRLN Discovery Steering Committee responsible for project management and technical implementation. Three smaller Implementation Teams — User Experience and Services, Data Extract and Ingest, and User Interface Development —  reported to the Steering Committee.

After consulting academic libraries and library consortia, conducting background research, and completing group and individual evaluations, the TRLN Discovery Steering Committee recommended that the Blacklight open source discovery system be used as the foundation for the new TRLN discovery service. The committee felt that both Blacklight and VuFind would fulfill the requirements of this project but noted that Blacklight’s modularity and extensibility would more readily facilitate collaborative development while also allowing local variation when necessary.

In May 2017, at the recommendation of the Advisory Team, TRLN implemented an Agile approach, specifically Scrum, for the implementation phase of the project. The teams and committees that had been involved with the project up to that point were reconfigured or dissolved as necessary in order to align with Scrum principles. TRLN financial and staffing resources went into the purchase of Jira and Confluence for project management.

Historic Timeline

TRLN organized a workshop on May 16 to distribute knowledge about the TRLN Discovery project among staff from all four member institutions. The workshop covered three major aspects of the project: the infrastructure in AWS, the web application, and data extract. A follow-up workshop will take place on June 6 to demonstrate and practice work related to Solr in AWS. The development team worked on improvements to search relevance and on blocking bot activity in the NCCU catalog. The Solr configuration was upgraded on May 21 to apply relevance updates. The team worked on more thorough documentation of various aspects of the project, most recently documenting how to restrict web crawlers and bots..
Changes were made to improve the accessibility of the catalog. The development team worked on a plan for Solr backups as part of an overall disaster recovery plan.
UNC-CH released a public Beta version of the new shared catalog on Monday, February 4.
The new catalog went live at NCCU on Monday, January 7; at NCSU on Monday, January 14; and at Duke on Wednesday, January 16. UNC-CH will release a public Beta version on Monday, February 4.