Done
Details
Assignee
Aditya matukumalliAditya matukumalliReporter
Anne L. HighsmithAnne L. HighsmithTester Assignee
Anne L. HighsmithAnne L. HighsmithPriority
P2Story Points
2Sprint
NoneDevelopment Team
ProkopovychTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Aditya matukumalli
Aditya matukumalliReporter
Anne L. Highsmith
Anne L. HighsmithTester Assignee
Anne L. Highsmith
Anne L. HighsmithPriority
Story Points
2
Sprint
None
Development Team
Prokopovych
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created March 1, 2019 at 5:38 PM
Updated April 26, 2019 at 1:45 PM
Resolved April 26, 2019 at 1:45 PM
This applies to our Q4 instance at Texas A&M (TAMU)
TAMU has 60 locally-created locations in its Q4 instance (https://folio-q4.library.tamu.edu/), all of which were created in batch by submitting json to the /locations endpoint. As required by the endpoint, all of the *.json records for locations contained a primaryServicePoint element. Yet, when these locations are viewed in Settings/Organization/Locations, most, but not all, appear NOT to have a primary service point assigned.
I have cross-checked this by doing a get on the location json for one location, e.g. 'stk', then a get on the id for the primaryServicePoint that is assigned to the 'stk' location. The service point exists and has the correct id. But its discoveryDisplayName doesn't display in Settings/Organization/Locations. An example is attached.
For a few locations, however, the assigned service point does display in the Settings/Organizations/Locations page. For example, the location codes that begin 'maps' do display the discoveryDisplayName for their assigned service point.