Requests
(UXPROD-790)
|
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Requests |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Debra Howell | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | Requests, cornell-access-services, delegate_candidate, requests, resourceaccess, ui-only-candidate | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue links: |
|
||||||||
| Epic Link: | Requests | ||||||||
| Development Team: | Vega | ||||||||
| PO Rank: | 0 | ||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||
| Rank: Duke (Full Sum 2021): | R2 | ||||||||
| Description |
|
Problem When staff are creating new requests on behalf of patrons, they do not always have the patron's barcode value available. Often, they are more likely to be given the user's externSystemId, username, or some other user attribute other than barcode. The patron lookup field in Requests > Create request should perform similar lookup functionality to the Check out app (ui-checkout). =====
Description: When you are in inventory on the item record, when you create a new request on the item (done a lot for new books), can you have the requester information automatically have the name or net id rather than the barcode? ** Feature components:
|
| Comments |
| Comment by Erin Nettifee [ 15/Sep/21 ] |
|
Reassigning to Brooks as the Requests PO |
| Comment by Erin Nettifee [ 15/Sep/21 ] |
|
Debra Howell - you have the requester lookup linked below - that may have been the approach judged best for this need, since you don't have access to the user search directly in that app, but the user search component can be triggered. I think that's the approach that apps outside of Users are taking (see circ log, check out.) But perhaps we can explore whether this is possible, since I agree it would be a smoother UI |
| Comment by Debra Howell [ 15/Sep/21 ] |
|
Thanks, Erin Nettifee - Andy Horbal can answer any questions and/or test. |
| Comment by Brooks Travis [ 10/Dec/21 ] |
|
I wonder how much trouble it would be to implement the same lookup code from ui-checkin in this component? |
| Comment by Stephanie Buck [ 13/Apr/22 ] |
|
Brooks Travis, is this still a relevant feature? I'm not sure I'm catching the nuances, here. |
| Comment by Brooks Travis [ 15/Apr/22 ] |
|
Yes. It would be very useful if the patron lookup field in Requests accepted the same lookup values as Check In.Stephanie Buck |
| Comment by Stephanie Buck [ 15/Apr/22 ] |
|
Thanks, Brooks Travis. I'm moving this into draft since there are no stories/requirements written yet. |
| Comment by Khalilah Gambrell [ 06/Sep/22 ] |
|
Hey Stephanie Buck, Erin Nettifee and Brooks Travis, I am reviewing this feature and I think https://bugfest-mg.int.aws.folio.org/ supports this feature request. When I click on the Requestor lookup... I am able to search by username, email, barcode, and external system ID. Or is the requirement to have the highlighted section
Which is powered by Settings selection
|
| Comment by Erin Nettifee [ 06/Sep/22 ] |
|
It's the latter Khalilah Gambrell - libraries want to just do the search without having to click the patron search popup. |