Requests
(UXPROD-790)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Requests |
| Type: | New Feature | Priority: | P4 |
| Reporter: | Cate Boerema (Inactive) | Assignee: | Thomas Trutt |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | requests, round_iv | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Epic Link: | Requests | ||||||||
| Front End Estimate: | Small < 3 days | ||||||||
| Front End Estimator: | Matt Connolly | ||||||||
| Front-End Confidence factor: | Low | ||||||||
| Back End Estimate: | Large < 10 days | ||||||||
| Back End Estimator: | Marc Johnson | ||||||||
| Estimation Notes and Assumptions: | Includes blocking creating (or changing type of existing) requests for the type in the API
Assumes we store this information in general configuration (and so no new settings record types are needed in the API) Assumes we will *not* block the various settings in policies in the API (as these are provided at storage, and have no availability of these settings) Includes making mod-circulation make requests to fetch these settings |
||||||||
| Development Team: | Vega | ||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 1 | ||||||||
| PO Rank: | 37 | ||||||||
| PO Ranking Note: | 2020-10-04 - CB: Making my PO rank same as the calculated total rank for now.
2019-07-12: Keeping PO rank same as calculated rank (with potential minor adjustments to avoid having two features with same rank) |
||||||||
| Rank: Chalmers (Impl Aut 2019): | R5 | ||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||
| Rank: FLO (MVP Sum 2020): | R4 | ||||||||
| Rank: GBV (MVP Sum 2020): | R2 | ||||||||
| Rank: Grand Valley (Full Sum 2021): | R2 | ||||||||
| Rank: hbz (TBD): | R2 | ||||||||
| Rank: Hungary (MVP End 2020): | R1 | ||||||||
| Rank: Lehigh (MVP Summer 2020): | R4 | ||||||||
| Rank: Leipzig (Full TBD): | R4 | ||||||||
| Rank: MO State (MVP June 2020): | R4 | ||||||||
| Rank: TAMU (MVP Jan 2021): | R4 | ||||||||
| Rank: U of AL (MVP Oct 2020): | R2 | ||||||||
| Description |
|
Institutions may not use all of the available request types in FOLIO. This feature is about providing a tenant-level settings for selecting the supported Request types (currently a selection of Recall, Page and Hold). This will ensure that:
Without this feature, it will still be possible to prevent requests of different types using request policies. This feature would just streamline the user experience. |
| Comments |
| Comment by Cate Boerema (Inactive) [ 29/Nov/18 ] |
|
Marc Johnson and Matt Connolly, can you please estimate this feature? Thanks! |
| Comment by Marc Johnson [ 04/Dec/18 ] |
|
Cate Boerema Jakub Skoczen Are we intending to create a new settings record type (like loans policy, fixed due date schedule) or keep it in the general configuration settings? |
| Comment by Cate Boerema (Inactive) [ 04/Dec/18 ] |
|
I think this setting would make sense in Settings > Circulation somewhere, as it will only be necessary when the Requests app is enabled. |
| Comment by Anya [ 29/Mar/19 ] |
|
Comment from the March meeting : it was thought that this was done ... |
| Comment by Anya [ 27/Jun/19 ] |
|
FC will be using all types so the default of all will work for us. |
| Comment by Holly Mistlebauer [ 07/Mar/22 ] |
|
This feature is marked DRAFT until Brooks Travis has a chance to review it for validity. |
| Comment by Erin Nettifee [ 15/Nov/22 ] |
|
If the work in
|