Done
Details
Assignee
Dima TkachenkoDima TkachenkoReporter
Brooks TravisBrooks TravisLabels
Priority
P3Story Points
8Sprint
NoneDevelopment Team
VolarisFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Dima Tkachenko
Dima TkachenkoReporter
Brooks Travis
Brooks TravisLabels
Priority
Story Points
8
Sprint
None
Development Team
Volaris
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created March 25, 2021 at 7:38 AM
Updated September 17, 2021 at 11:19 AM
Resolved June 17, 2021 at 2:21 PM
Purpose/Overview:
INN-Reach uses a flat location structure that does not distinguish between branches ("libraries" in FOLIO) and shelving locations ("locations" in FOLIO). Therefore, the FOLIO system administrator or other user with appropriate permissions must provide a mapping between these records in FOLIO and an INN-Reach compatible code/description combination. The INN-Reach location code/description options should be loaded/managed as reference data by a user with appropriate permissions and referenced by ID (or code) in the mapping model (MODINREACH-17)
Requirements/Scope:
Mapping should be per local server/central server combination
Mapping must support having either a Library or shelving location ("Settings > Tenant > Location Setup") correspond to an INN-Reach location code/description
The same code/description can apply to multiple FOLIO location-like objects (libraries or locations)
If not specified, the shelving locations should inherit the mapping for their parent library
The inheritance applies until a mapping is explicitly specified for a shelving location
The situation in which the mapping will be used is to convert a FOLIO location into an INN-Reach code for transmission to the server as part of record contribution. The model should be structured accordingly
There should be some mechanism for indicating that a library and/or location is intended for INN-Reach circulation-only use and ignored for purposes of mapping validation
To begin with, this indication will not be managed, and we should avoid creating libraries and locations for these purposes
Later development will account for this functionality when the circulation agency-to-location mappings are implemented
Approach:
Acceptance criteria:
AC: A mapping configuration record/records can be created, retrieved, updated, and deleted from the database