Requests
(UXPROD-790)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Quesnelia (R1 2024) | Parent: | Requests |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Stephanie Buck | Assignee: | Stephanie Buck |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | loc, requests, resourceaccess | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Release: | Quesnelia (R1 2024) | ||||||||
| Epic Link: | Requests | ||||||||
| Front End Estimate: | Small < 3 days | ||||||||
| Front End Estimator: | Stephanie Buck | ||||||||
| Front-End Confidence factor: | 60% | ||||||||
| Back End Estimate: | XL < 15 days | ||||||||
| Back End Estimator: | Stephanie Buck | ||||||||
| Back-End Confidence factor: | 40% | ||||||||
| Development Team: | Vega | ||||||||
| PO Rank: | 0 | ||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||
| Description |
|
Current situation or problem: It is not possible to disallow title level requesting for items in certain locations (or libraries.) In scope Out of scope Use case(s) A single FOLIO institution has several general collection libraries and one library that has special collections. The general collection libraries want to have title-level requesting; the library with special collections does not. Proposed solution/stories Links to additional info Questions |
| Comments |
| Comment by Stephanie Buck [ 30/Jan/23 ] |
|
Is this scenario about disallowing title level requests for special collections/certain locations, or is it special collections/certain locations only want item level requests, or should requests of any type not be allowed? Erin Nettifee, do you have any idea? |
| Comment by Erin Nettifee [ 30/Jan/23 ] |
|
I could see all of those use cases, Steph. At Duke, we would want TLR for some of our general collection, and item level only for some of our general collection, and for special collections, we would want item-level for some parts of the collection, and no requests at all for other parts of the collection. E.g., you always have uses cases for things that have been collected but have restricted access until a certain time period has passed, or a particular donor dies, things like that. I think the approach I would want, all else being equal, would be one where the circulation rules drive what happens. So I can look at a circulation rule and determine whether item level or title level requesting was allowed, or both. I don't want to maintain a separate table that controls TLR access.... |
| Comment by Stephanie Buck [ 31/Jan/23 ] |
|
Thanks, Erin. This is helpful. |
| Comment by Erin Nettifee [ 31/Jan/23 ] |
|
A more general (and I think very typical) use case for Duke would be allowing title-level requesting for items in our stacks and at our remote storage, but not on course reserve. It would be very common for us to have a popular textbook where a few copies are in the stacks and a few copies are on reserve. (Whether it's an actual textbook, or, say, a copy of a classic novel.) E.g., we might have 8 copies of the organic chemistry textbook, and four of them are in the stacks and can be borrowed for a semester, and four of them are behind the desk and can be borrowed for a few hours. Depending on the item, they could even be copies that are all on the same instance. That's why the idea of the circ rule controlling what happens feels like what I would want - because we're already applying that level of control for item-level requesting. |
| Comment by Thomas Trutt [ 08/Feb/23 ] |
|
Id agree with Erin. Considering the above discussion should this ticket be closed or combined with
|
| Comment by Stephanie Buck [ 21/Mar/23 ] |
|
|