Bug 38864 - API functionality needed in patron message to allow future connectivity with discovery systems
Summary: API functionality needed in patron message to allow future connectivity with ...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-10 18:07 UTC by Christopher Brannon
Modified: 2025-02-25 15:37 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Brannon 2025-01-10 18:07:05 UTC
I would like to see API functionality added for patron messages (particularly the OPAC messages) so that down the road, discovery systems like Aspen could develop more connectivity with Koha and other ILS systems to allow those messages to have the option to notify patrons on their accounts in discovery.  Right now, that is a major gap when using a discovery system.  We can communicate with the patron in their account in the OPAC, but not through their account in Aspen, or other third party catalogs.

This would need to include a way for messages to be discovered by the discovery system and a way to set the read flag (a newer feature in Koha) so that patrons can mark the message as read and staff can see it has been read.