Store patron's cached municipality code to circulation events. #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sylvain-degeilh-lingsoft
approved these changes
Apr 18, 2024
ttuovinen
deleted the
feature/simplye-239/store-location-to-patron-events
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Change circulation analytics to store patron's municipality code ("cached_neighborhood") to circulation events in local db and OpenSearch.
Motivation and Context
This change will eventually enable municipality-specific statistics for librarians. Relates to: https://jira.lingsoft.fi/browse/SIMPLYE-239
How Has This Been Tested?
I Tested this locally with patron borrowing, opening and returning books and location data was stored in circulationevents rows and OpenSearch documents. Related automated tests have been updated.
Checklist