Send request- related notices (time based)

Context
Requests include page, hold and recall requests. For each of these scenarios, exact timing and conditions are determined by a combination of notice policies and circulation rules, and exact wording is determined by templates. Each of these specific scenarios may or may not be used by every institution. If there's no corresponding policy defined in settings, then these scenarios won't apply.

—

Page
Paging requests include items that are currently available (and not checked-out by another patron). These items are pulled from their home shelf and put on the service point's hold shelf for pick-up by the patron that requested the item. The paging request process prompts several patron notices. Specific time-based notices are outlined below:

Scenario 1
Given a page requested item
When it is not picked up and/or it's nearing hold expiration
Then send a reminder notice to requester
(May be none to many sent depending on when the item is returned and policy settings.)

Scenario 2
Given a page requested item with a status of awaiting pick-up
When it is not picked up and its hold expires
Then send a hold expiration notice to requester

Scenario 3
Given a page requested item
When the request period expires (might not have been found by staff?)
Then send an request expiration notice to requester

—

Hold (previously CIRC-388)
Hold requests include items that are currently checked-out by another patron (Patron A). A hold request restricts Patron A from renewing the item. This differentiates it from a recall request where Patron A must return it sooner than the original due date/time. Once the requested item is returned, it is routed to the requested location, if necessary, and then placed on the hold shelf. The hold request process prompts several patron notices. Specific time-based notices are outlined below:

Scenario 1
Given a requested item for hold with a status of awaiting pick-up
When it is not picked up and/or it's nearing hold expiration
Then send a reminder notice to requester (Patron B in diagram)
(May be none to many sent depending on when the item is returned and policy settings.)

Scenario 2
Given a requested item for hold
When it is not picked up and its hold expires
Then send an hold expiration notice to requester

Scenario 3
Given a requested item for hold
When the request period expires
Then send an request expiration notice to requester

—

Recall
Recall requests include items that are currently checked-out by another patron (Patron A). Recall requests typically ask Patron A to bring the item back before it's original due date/time. Once the requested item is returned, it is routed to the requested location, if necessary, and then placed on the hold shelf. The recall request process prompts several patron notices. Specific time-based notices are outlined below:

Scenario 1
Given a recalled item
When its due date/time is nearing
Then send a courtesy notice to patron (A in diagram) that currently has it checked-out to remind them of the due date/time
NOTE: This is a regular courtesy notice (because the current borrower's due date/time changed).

Scenario 2
Given a recalled item
When it is overdue
Then send an overdue notice to patron (A in diagram) that currently has it checked-out to remind that their item is past due and/or any fines that may be incurred
NOTE: This is a regular overdue notice (because the current borrower's due date/time changed).

Scenario 3
Given a recalled item with a status of awaiting pick-up
When it is not picked up and/or it's nearing hold expiration
Then send a reminder notice to requester (Patron B in diagram)

Scenario 4
Given a recalled item
When it is not picked up and its hold expires
Then send a hold expiration notice to requester (Patron B in diagram)

Scenario 5
Given a recalled item
When the request period expires
Then send a request expiration notice to requester (Patron B in diagram)