Summary: | Add an endpoint to list effective circulation rules for an itemtype, branchcode, patron category combination | ||
---|---|---|---|
Product: | Koha | Reporter: | Martin Renvoize <martin.renvoize> |
Component: | REST API | Assignee: | Martin Renvoize <martin.renvoize> |
Status: | Needs Signoff --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | mspinney, tomascohen |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19037 | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Bug Depends on: | |||
Bug Blocks: | 34440 | ||
Attachments: | Bug 36641: Add endpoint for fetching circulation rules |
Description
Martin Renvoize
2024-04-18 12:45:08 UTC
Created attachment 165086 [details] [review] Bug 36641: Add endpoint for fetching circulation rules This patch is a proof of concept for an API endpoint that returns a list of circulation rules for the specified itemtype, branchcode and patron category combination. You can also add a list of `rules` as a query parameter to limit the response to only the rules you are interested in for this combination. Setting to NSO to get eyes.. but right at this moment it would fail QA for lack of tests. I want feedback specifically on the URL and the form of the response and if we're happy for it to be an open object or want to a spec for it with each of the available circ rule keys listed but optional. A few remarks: * The order of the path parameters is arbitrary, right? I assume you thought about it * The parameter names should be fixed to our current uses * The returned structure is under specified * I never liked /circulation-rules, can we make it /circulation_rules so it matches all other routes? |