Details
-
Story
-
Status: Closed (View Workflow)
-
P1
-
Resolution: Done
-
None
-
-
Core: F - Sprint 57, Core: F - Sprint 58
-
20
-
Prokopovych
Description
Assumptions
- Resolving request policies follows the same rules as for loan policies, as described here
Outstanding Decisions
- Should this include validation that the request policy exists when the rules are changed? (julianladisch Does the existing API do this for loan policies?)
API Design
How do we want to reflect the ability to evaluate the rules for different policy types in the API?
Scenarios
These are broad scenarios. If useful they can be expanded with respect more of the loan rules matching rules.
Scenario 1
- Given loan rules with a matching rule for a request policy R
- When the rules are applied
- Then request policy R is provided
Scenario 2
- Given loan rules with no rules matching for a request policy
- And a fallback policy that includes request policy R
- When the rules are applied
- Then request policy R is provided
Scenario 3
- Given loan rules with no rules matching for a request policy
- And no fallback policy that includes a request policy
- When the rules are applied
- What should happen? (julianladisch What is the behaviour for loan policies at the moment?)
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-1217 Extending Loan Rules Editor to target additional policy types
-
- Closed
-
- has to be done after
-
CIRC-187
Back end work for UICIRC-164 and UICIRC-165: Include request policy and patron notice policy in circulation rules syntax
-
- Closed
-
- has to be done before
-
CIRC-230
Backend Work for UIREQ-211: Apply Request Policy on Creation
-
- Closed
-
- relates to
-
-
- Closed
-
-
CIRC-220 Improve description of loan policy returning endpoints
-
- Closed
-
-
CIRC-239 Apply circulation rules directly rather than via API endpoint
-
- Closed
-
-
CIRC-197
Back end work for UICIRC-164 and UICIRC-165: Determine patron notice policy based upon loan rules
-
- Closed
-
-
-
- Closed
-
