OpenRS Town Hall Q&A
The following questions were submitted during the recent OpenRS Town Hall, which provided an opportunity for library staff and community members to learn more about OpenRS functionality, integrations, workflows and future development plans.
A recording of the Town Hall is available here.
Is there a limit on the number of OpenRS users per organization? Would there be an additional cost if an organization needs more staff logins?
There is no limit on the number of OpenRS users or logins per organization, and there is no additional cost for more staff logins.
Did MOBIUS have a shared index or catalog before adopting OpenRS?
Yes. MOBIUS previously used INN-Reach, which is also a DCB model resource sharing system.
When an item is “in transit” in the system, can any field in the request be altered during that time, either in the ILS or OpenRS?
This depends on the ILS or LSP being used. Please reach out so we can discuss the specifics of your system and workflow.
Does the OpenRS app for FOLIO print address labels for shipping? Does it support article or chapter scan requests? Is that what is meant by document delivery?
For ILL and document delivery, the pull slip is generated through third-party software called JasperReports, which is integrated with ILL. Users can create pull slips externally and upload whatever pull slip configuration they would like.
More information about JasperReports is available here: https://github.com/Jaspersoft/jasperreports.
Can you share more about the planned Universal Connector? I work with a group of libraries spread across many systems, and WMS is one of the main ones.
The Universal Connector, also known as the Foundation Connector, is how OpenRS intends to support library systems that do not currently have an adapter.
The OpenRS Foundation Connector will allow libraries to support the DCB standard workflow by leveraging an industry-wide standard circulation protocol, such as SIP2, with an OpenRS Customization Service. It also includes the OpenRS Record Uploader for libraries without an OAI-PMH endpoint.
By providing new OpenRS Customizations, community members can contribute new integrations or improve existing ones.
Would we be expected to use an ILL app in FOLIO for OpenRS instead of ILLiad? Is the goal for the OpenRS app in FOLIO to ingest requests from other systems, such as Rapid, OCLC or Docline, and replace ILLiad? Will OpenRS connect with ILLiad? Will this be a separate system for ILL statistics?
OpenRS does not place any expectations on libraries to use one system over another. DCB and ILL can work independently or alongside each other.
OpenRS will not ingest historical requests from other systems, but it can accept requests from other systems using ISO 18626.
OpenRS does not currently connect with ILLiad because ILLiad uses ISO 10161. Connecting OpenRS with ILLiad would require development work, and OpenRS would be interested in working with partners who want to support that effort.
OpenRS ILL will be a place to create, manage and report on ILL requests with any system that can accept and send ISO 18626 requests.
Is OpenRS a replacement for ILLiad?
OpenRS ILL allows libraries to create, manage and report on ILL requests with any system that can accept and send ISO 18626 requests.
Is it possible to add a “pick up electronic item” option on the request form, where users choose a delivery option?
This is on the roadmap and is currently being worked on. A digital lending workflow is expected to be in place by the end of the year.
Does OpenRS use regular check-in rather than ILL check-in in Polaris?
Yes. OpenRS DCB uses the circulation APIs and corresponding circulation workflows within Polaris, Alma, Sierra and FOLIO.
For Sierra libraries, does RTAC remove the need for the traditional virtual record used by INN-Reach?
RTAC stands for real-time availability checking. RTAC is used by Locate to retrieve circulation status data from individual library systems for display and requesting operations.
OpenRS temporary instance, item and patron records are distinct from FOLIO instance, item and patron records. The implementation of OpenRS FOLIO virtual records differs completely from that of INN-Reach virtual records in Sierra.
In Alma, Sierra and Polaris, OpenRS has leveraged the inventory and user APIs to create legitimate inventory and user records in each system. When the request is complete, OpenRS deletes the temporary records.
Is SirsiDynix integration available, or is it being considered for the future?
Work to integrate SirsiDynix is not currently scheduled. If you are interested in becoming a partner for this adapter, please reach out to info@openrs.org.
Initially, SirsiDynix systems will be supported through the new Foundation OpenRS DCB Connector referenced in the roadmap. This will deliver core OpenRS DCB functionality and allow libraries using these systems to participate.
Some functionality, such as Pickup Anywhere, will not be available at launch. However, the OpenRS DCB participation model, combined with OpenRS’s open-source nature, will allow community members to improve the SirsiDynix Foundation integration or contribute to a future adapter with full functionality.
The OpenRS Foundation Connector differs from existing adapters by using a combination of available protocols, such as NCIP and SIP2, and API-based customizations to support library participation in OpenRS. This delivers the standard workflow for library systems that do not currently have an adapter, ensuring they can still participate in DCB.
Currently at DPL, consortium items are placed in a separate tab in Polaris. Is there a way they are tagged when using OpenRS?
Within Polaris Leap, virtual items have a single and distinct location.
Is anyone working on Evergreen ILS integration?
Not currently, but OpenRS would like to pursue Evergreen integration. There has definitely been interest.
With OpenRS, staff would not see what is paged in Polaris, correct? Would they need to log into OpenRS?
Fortunately, no. To see what is paged in Polaris Leap, the library would view the picklist for their pickup location.
Is there functionality for staff mediation of requests placed by patrons, such as approve or disapprove?
This is not currently available in OpenRS DCB, but it is available in OpenRS ILL.
Does DCB Admin replace ILL Request Manager in Polaris, or will that level of integration remain?
DCB Admin does not replace the ILL Request Manager in Polaris. The integration for OpenRS DCB is directly into the Polaris Circulation module, not the ILL module.
We use Evergreen as a consortium with 52 different library systems. Each of those systems currently manages its own ILL requests. Would they still be treated as 52 different systems even though they share an ILS?
OpenRS has not yet been developed against the Evergreen API. However, based on an initial review of the API, it seems likely that each library would be treated as separate from the other libraries.
FOLIO is very strict about creating features for pickup points. Will the checkout period default to the pickup point, or to the GWLA reciprocal ILL agreement timeframe?
The checkout of FOLIO virtual items is governed by the matching circulation rules and does not require an associated pickup service point.
In terms of deduplication and clusters in the admin interface, if a book is grouped incorrectly, can an administrator dedupe it in the consortial view, or do they need to contact support?
DCB Admin’s cluster explanation feature details why a record, or set of records, has been clustered.
Consortium and library administrators can use this feature to identify data issues in the associated records, which they can then resolve in the ILS.
If the issue is with the clustering process, staff can also share the link with support, which can resolve or escalate it.
Are there different levels of staff access in OpenRS?
Yes. There are three levels of staff access in OpenRS:
Does OpenRS support Z39.50 queries?
OpenRS ILL does not support this functionality. External libraries that use Z39.50 would search the FOLIO Inventory app directly rather than search in OpenRS.