Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

CIRC-2269: [ECS TLR] Send request create notification when the patron is resolved

Description

  1. In the mod-circulation code in replaceRequest method should be adjusted to identify that the fake patron was resolved to the real one.

  2. One possible option to understand that a patron is fake is to use this approach. But the preferable option is to check if there was no email address of the patron in an old version of the request

 

Technical solution:

Environment

None

Potential Workaround

None

Attachments

7

Checklist

hide

Activity

Show:

Anne Ekblad March 17, 2025 at 1:06 PM

Hi, and . I see Polina’s comments. Thank you, and I will review them for any potential concerns.

Irina Pokhylets March 14, 2025 at 10:54 AM

Works as expected, notifications for secure requests are sent to the partner upon creation, cancellation, and awaiting pickup.

Polina Ustimenko March 13, 2025 at 5:42 AM

Tested on ECS eureka snapshot.

Notification for item-level Page Mediated request:

Notification for item in status Awaiting pickup:

Notification for item-level request cancellation:

Notification for item-level Hold Mediated request:

Notification for title-level Page Mediated request:

Notification for title-level Hold Mediated request:

Notification for cancellation of title-level Hold Mediated request:

Issues to discuss:

  • Recall type mediated requests notifications do not arrive, even for circulation ECS requests

  • Hold shelf expiration notice is not sent, even for circ ECS and local requests. Also there’s no “Hold shelf expiration date” field in mediated request page

  • Similar situation with Request expiration notice - there’s no possibility to set expiration date for a mediated request, maybe it’s not applicable here? Usual request expiration notice is sent (for circulation ECS request)

  • Proxy/sponsor functionality is not applicable for mediated requests

could you please review the functionality and discuss problematic parts with Vega PO and LoC representatives? It’ll be nice to know what exactly from listed scenarios should work. Thank you

cc:

Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Volaris

Release

Ramsons (R2 2024) Service Patch #1

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created February 24, 2025 at 8:23 AM
Updated last week
Resolved March 14, 2025 at 10:55 AM
TestRail: Cases
TestRail: Runs