Consortial FOLIO Integration
Implementation Milestones
See MOBIUS DCB Functional Release Planning
Pre-Requisites
Definitions Required: expected workflow, lms interface, expected behaviour, alternative vocabulary
Data required: mappings, configs
Dependencies: technical, workflow
Note: non-volume requests only
Goal / Item | Definitions Required | Data Required | Dependencies |
---|---|---|---|
Ingest from consortial FOLIO tenants |
|
| DCB-797: Parse instance ID from FOLIO OAI-PMH identifierClosed |
Check live availability of requested item |
|
|
|
Authenticate patron from consortial FOLIO library |
|
|
|
Validate patron from consortial FOLIO library |
|
| https://openlibraryfoundation.atlassian.net/browse/DCB-766 Changes in validatePatron flow for FOLIO to accommodate how we compensate for home library code add default agency code config setting for each host LMS |
Place request to supply from consortial FOLIO library DCB-490: Place request in lending library on FOLIO systemClosed |
| Mappings
| Change to edge-users to return both patron group UUID and name |
Place request to borrow from consortial FOLIO library |
|
| Extend PlaceHoldRequestParameters |
Circulate requests involving consortial FOLIO libraries as supplier DCB-825: Circulate requests involving consortial FOLIO libraries as supplierClosed |
|
| |
Circulate requests involving consortial FOLIO libraries as borrower DCB-826: Circulate requests involving consortial FOLIO libraries as borrowerClosed |
|
|
|
Handle patron cancellation DCB-827: Handle patron cancellation of consortial FOLIO requestsClosed |
|
|
|
Finalise completed requests |
|
|
|
Unknowns
unknown blocking workaround with expected consequences resolved
Parameters needed to define pickup location for a DCB transaction
19 Dec: discussed in cross-development and further investigation underway by Tim / Volaris
21 Dec: DCB only needs to provide service point id for the pickup location (and not name or code)
require mapping for: pickup location to agency code
require mapping for: agency code to service point id
Ingestion strategy
19 Dec: decided in cross-dev that we will be ingesting on a per tenant basis
Will need development work to parse the instance ID from the OAI-PMH identifier (DCB-797)
How the DCB transaction status lines up with the item and request status based tracking implementation
The potential impact of this is likely better discussed with @Ian Ibbotson (Use this one)
It could require some refactoring to the current tracking implementation
Relates to the
chain of responsibility
topic discussed in cross-dev on 19 DecFollowup call scheduled for 2 Jan 2024
How well the DCB transaction API differences can be hidden within the current Host LMS client without further refactoring
Additional mappings required
References
Jira Ticket
TBD Implement FOLIO Circulation Lifecycle
FOLIO Reference:
Related Documentation
Operated as a Community Resource by the Open Library Foundation