Requests (UXPROD-790)

[UXPROD-69] Request policies (CRUD and Impact on Requests) Created: 18/Jan/18  Updated: 16/Sep/20  Resolved: 26/Mar/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q1 2019
Parent: Requests

Type: New Feature Priority: P3
Reporter: Cate Boerema (Inactive) Assignee: Cate Boerema (Inactive)
Resolution: Done Votes: 0
Labels: q1-2019-at-risk, requests, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by UXPROD-1217 Extending Loan Rules Editor to target... Closed
Defines
is defined by UIREQ-211 Make Request Policy Effective At Requ... Closed
Relates
relates to UIREQ-181 Request Policy CRU v1 Closed
relates to UICIRC-163 Permission Set for Request Policy CRUD Closed
relates to UIREQ-183 Request Policy Delete Closed
relates to UIREQ-184 Add Last Updated Record Metadata to R... Closed
relates to UXPROD-1217 Extending Loan Rules Editor to target... Closed
Epic Link: Requests
Analysis Estimate: XL < 15 days
Analysis Estimator: Tania Fersenheim
Front End Estimate: XL < 15 days
Front End Estimator: Kostyantyn Khodarev
Front-End Confidence factor: Low
Back End Estimate: XXL < 30 days
Back End Estimator: Marc Johnson
Estimation Notes and Assumptions: assumes separate from Loan rules & polcies

Old estimates FE Large (Matt C)
Development Team: Prokopovych
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: GBV (MVP Sum 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

What's included in this feature:

  1. Allow the creation and management of request policies
  2. Make request policies effective at the time of request creation (FOLIO will use the extended loan rules editor (see UXPROD-1217 Closed ) to determine which request policy applies to each request
    1. Like loans, requests are made between users (requester) and items. To determine the appropriate request policy, FOLIO will run the patron group of the requester specified in the request as well as the material type and item type (and, later, the location) of the requested item through the Loan/circ rules to determine which request policy applies
    2. Then, in the request app, the request will either be allowed or disallowed and the appropriate pickup and delivery options should display (per the request policy settings)

Long term vision for request policy: Eventually the request policy will allow you to say, for each type of request in FOLIO, whether the request type is allowed, whether pickup is allowed and where and whether delivery is allowed. See mockup here: https://drive.google.com/file/d/1ok58OxvZKQPPW1EY2ZyB6qAfkLPcCZmf/view

Possibly interim step: If the developers think this is easier, we could simplify the request policy for Q1 2019 and have something like this: https://drive.google.com/file/d/1tEROnIyNtBWBukQ-ftbQVsn_IdtgTTst/view?usp=sharing FOLIO would just assume that both delivery and pickup are possible for all requests.



 Comments   
Comment by Theodor Tolstoy (One-Group.se) [ 25/Oct/18 ]

Does this include the logic of controlling which items can be requested and which cannot?

What will happen without this? Will all books be requestable to everyone or will no one be requestable?

Comment by Cate Boerema (Inactive) [ 25/Oct/18 ]

Does this include the logic of controlling which items can be requested and which cannot?

Yes, among other things. We are discussing in the RA SIG today if you want to join! Here's the early wireframe we'll be reviewing: https://drive.google.com/open?id=1EUQ3yCfjqjsk2amiPUK7SHqQEcY1hSd8

What will happen without this? Will all books be requestable to everyone or will no one be requestable?

All books will be requestable to everyone (as is the case in FOLIO today).

Comment by Theodor Tolstoy (One-Group.se) [ 25/Oct/18 ]

Thank you Cate Boerema,
I will discuss it with Chalmers and get back to you.

There are some obvious issues with this. For example Reference literature.

Comment by Cate Boerema (Inactive) [ 08/Jan/19 ]

Reassigning to Core, as Vega no longer has capacity. Okayed by Jakub.

Comment by sthomas (Inactive) [ 09/Jan/19 ]

Cate Boerema While UXPROD-1217 Closed is a blocker for "impact on requests", this issue blocks UXPROD-1217 Closed on "request policy CRUD" as the Circulation Rules editor will not be able to fetch Request Policies that don't exist in Settings>Circulation>Request policies. Right?

Generated at Fri Feb 09 00:05:29 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.