Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Agency to FOLIO Location Mapping Settings Not Listing all Available Libraries

Description

Overview:

In the Agency to FOLIO location mapping settings section, the library selection form fields should list all available FOLIO libraries (actually, it should be all FOLIO libraries not already mapped to a local agency, but I can't recall if that was implemented yet or not). However, in GVSU's tenant it is listing only one library (with no clear indication of why).

Steps to Reproduce:

  1. Log into GVSU's FOLIO tenant

  2. Open Settings > INN-Reach > Circulation > Agency to FOLIO locations

  3. Select the MeLCat central server

  4. Attempt to select a FOLIO library to assign as the default location for the central server (or any other local server/agency)

Expected Results:

The list of FOLIO libraries includes (at least) all the libraries not mapped to a local agency in the central server configuration.

Actual Results:

Only one library is listed (more than one is defined and not already mapped to a local agency).

Additional Information:
URL:
Interested parties:

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Tim Auger September 7, 2022 at 7:22 PM

I tested the change and was unable to reproduce the problem. 

Tim Auger September 1, 2022 at 11:06 PM

for this and the other two issues, is release in MG combined with API workarounds, sufficient for the need to keep on-track with D2IR verification?

Mikita Siadykh September 1, 2022 at 6:01 PM
Edited

hi  

I can't reproduce this on https://volaris.ci.folio.org/, there are several libraries available there, this list displays libraries connected to central server (https://volaris.ci.folio.org/settings/innreach/central-server-configurations/b19a50d5-6757-4ba9-91a5-0c00fbb67962/view)

additionally there was some work done in MG in scope of https://folio-org.atlassian.net/browse/UIINREACH-150 to change a way to work with API, there is a chance it fixed

please review on our rancher env

Brooks Travis September 1, 2022 at 1:14 PM

 Here's another one. I suspect I can also address this via the APIs directly, but want to get it on the radar. If we can resolve it via API, we can bump it down to a P2.

Done

Details

Assignee

Reporter

Labels

Priority

Sprint

Development Team

Volaris

Release

Morning Glory (R2 2022) Bug Fix

RCA Group

Implementation coding issue

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created September 1, 2022 at 1:13 PM
Updated September 22, 2022 at 1:16 PM
Resolved September 7, 2022 at 7:22 PM
TestRail: Cases
TestRail: Runs