FAQs

• What is the difference between OpenRS and ReShare?

  OpenRS and ReShare are both open source resource sharing platforms that share a common code base as an ancestor.  ReShare’s focus is primarily on ISO18626 interlibrary loan transactions and providing a stand alone interface for use by patrons and library staff to manage transactions.  OpenRS is focused on the spectrum of resource sharing methodologies, incorporating workflows that accommodate various levels of mediation by library staff.  This includes direct consortial borrowing for handling resource sharing at scale within and between consortia.  OpenRS integrates directly with multiple ILS/LMSs and Discovery products, eliminating the need for a stand alone interface.

• Is OpenRS exclusively an EBSCO product?

  No, OpenRS is fully open source. It is an official project of the Open Library Foundation and its code is freely available to all from Github. OpenRS integrates with any standards-based ILS or resource sharing systems including open source and proprietary systems. Any consortia or library can host OpenRS themselves, or work with open source vendors for OpenRS hosting, implementation, or development support.

• Is OpenRS restricted to EBSCO Locate as the discovery/OPAC layer?

  No, OpenRS is discovery agnostic. Libraries may use either commercial or open source interfaces and central indexes in conjunction with OpenRS.

• What does “DCB” mean?

  DCB or “Direct Consortial Borrowing” is an acronym intended to convey the seamless integration of libraries in a tightly integrated resource sharing network. In a DCB network workflows are primarily unmediated and presented through standard ILS operations such as holds, paging and circulation. DCB systems are characterized by having no special ILL interface and consortial borrowing intermixed with local circulation. DCB systems can be contrasted with traditional ILL systems which often have specialist workflows capable of dealing with the unique or special interlending requirements. DCB systems require some detailed configuration to set up initially, but outperform older models in terms of delivery time and first-to-fill metrics.

• What ILSs work with OpenRS?

  This is a list of ILS systems that can integrate with OpenRS for direct consortial borrowing. If you have a need to integrate with an ILS that is not on this list, please reach out to info@openrs.org.

  • FOLIO (done)
  • Sierra (done)
  • Polaris (done)
  • Alma (pending)
  • Evergreen (requested)
  • Follett (requested)
  • Apollo (requested)
  • SirsiDynix Symphony (requested) 
  • SirsiDynix Horizon (requested)

• What resource sharing systems will work with OpenRS?

  Any standards-based, ISO 18626 compliant system should be easy for OpenRS to integrate.

• Who do I contact if I want more information?

  Send an email to info@openrs.org

• Can I host OpenRS locally?

  Yes. Any consortia or library can host OpenRS themselves, or work with open source vendors for OpenRS hosting, implementation, or development support.

  There is a growing collection of resources for hosting providers on the project Wiki at: https://openlibraryfoundation.atlassian.net/wiki/spaces/DCB/overview?homepageId=2692907009. Specifically, see troubleshooting run books 

• Is there a discussion list and/or Slack channel for OpenRS?

  Yes.  In the Open Library Foundation Slack, look for #openrs-general

• How do I keep up with news concerning OpenRS?

  OpenRS Slack channel

• Is OpenRS built off INN-Reach

  No. While conceptually it performs some functions similarly to INN-Reach, OpenRS is not built off any INN-Reach code.

• Is OpenRS being built from scratch?

  No, both the architectural design and the code itself are based on work that dates back to before the conception of ReShare, though OpenRS code has been substantially updated and refreshed.

• Is OpenRS a fork of ReShare?

  No, although OpenRS and ReShare share a common ancestor, so both have some of the same components of that original code base.