Current situation or problem:
In an INN-Reach consortium, each participating local server must maintain a mapping of patron types configured on the INN-Reach central server and FOLIO patron groups to determine if a request is permitted.

In scope

• A system to manage mapping between FOLIO patron groups and INN-Reach patron types.

• A mechanism for periodically retrieving the list of central patron types and alerting a system admin that an action is required (eg. a central patron top is added/removed).

• A mechanism for detecting changes in local patron groups that could "break" the configured mapping and a process to alert a system administrator or prevent the change.

Out of scope
N/A

Use case(s)

Proposed solution/stories
System administrators should be able to use a FOLIO settings interface to manage the mapping configuration between FOLIO patron groups and INN-Reach patron types. One INN-Reach patron type should be mappable to multiple folio patron groups. This interface should also provide a method for manually updating the list of patron types from the central server or alerting system administrators when such an update has led to a mismatch in the configured map.

Links to additional info

Questions

• What mechanism can be used to notify the INN-Reach FOLIO module(s) to evaluate a change to a FOLIO patron group?

• How can system administrators be notified when an update to FOLIO patron groups requries action?

• How can system administrators be notified when the central patron type list does not match the configuration on the local server?

• What kind of interface should be used to manage this functionality for multiple INN-Reach central servers?