[UXPROD-3494] Resolve issues encountered by having one place process material requests for two Service Points Created: 07/Jan/22 Updated: 14/Feb/22 |
|
| Status: | Draft |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | TBD |
| Type: | New Feature | Priority: | P2 |
| Reporter: | Holly Mistlebauer | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | cornell-access-services | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||
| Issue links: |
|
||||||||||||
| Development Team: | None | ||||||||||||
| PO Rank: | 0 | ||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||
| Rank: Duke (Full Sum 2021): | R3 | ||||||||||||
| Description |
|
Background Overview Solution
Contact(s) Notes
|
| Comments |
| Comment by Erin Nettifee [ 11/Jan/22 ] |
|
What is the separate solution that Brooks Travis Thomas Trutt and Holly Mistlebauer discussed? |
| Comment by Brooks Travis [ 11/Jan/22 ] |
|
Grouping service points, so that if you check an item in at any service point in the group that it’s routing destination is in it’s like you checked it in at the destination. |
| Comment by Erin Nettifee [ 11/Jan/22 ] |
|
Brooks Travis so you're really talking about the grouping service points as pickup locations, right? On the Request record? We have that idea of a secondary service point, but in thinking about it I'm not sure that requests ever looks at secondary service point, it just looks at the pickup point chosen. Another thought might be a service point config option - where you can say "pickup location = yes" but "fulfilled at" choose another service point, and then in Cornell's use case, you'd say that the unattended pickup is a pickup location, but fulfilled at Olin.... It might be worth a tech spike to explore the needed technical approach.... |
| Comment by Brooks Travis [ 11/Jan/22 ] |
|
I’m thinking of something more generic, not just for pickup locations. |
| Comment by Erin Nettifee [ 11/Jan/22 ] |
|
So I'll ask the basic question, why is the contactless service point a service point at all? Is it just for the pickup location functionality? |
| Comment by Erin Nettifee [ 11/Jan/22 ] |
That's kind of what secondary service points are, it's just on the location level where it's configured. If an item's home location is A, and location A has primary service point B and secondary service point C, and I check it in while I'm logged in at service point C, it doesn't put it in route again, it moves it to Available. |
| Comment by Brooks Travis [ 11/Jan/22 ] |
|
Yeah, but I'm thinking of something that's configured at the service point level. |
| Comment by Holly Mistlebauer [ 11/Jan/22 ] |
|
The Circulation POs group meet on January 11 to discuss this issue. What Cornell is looking for is something like this...
MO State has a similar situation that they are addressing outside of FOLIO. It would be good to do this within FOLIO. Also, Chalmers has asked for something like this. Holly will bring this issue to the RA SIG for further discussion. We need to find out who, if anyone, else is impacted and come up with a solution that will work for everyone. Before the meeting with the RA SIG, Cornell needs to identify various use cases in a google document. The use cases will be presented to the Circulation POs at their January 18 meeting in preparation for the January 24 RA SIG meeting. |
| Comment by Debra Howell [ 11/Jan/22 ] |
|
Andy Horbal and Thomas Trutt Please see Holly's request above for use cases in a Google document in advance of the January 18th meeting with the Circ POs |
| Comment by Holly Mistlebauer [ 11/Jan/22 ] |
|
Debra Howell and Andy Horbal: Tom and I will be meeting on Thursday to create the use cases together. |
| Comment by Holly Mistlebauer [ 14/Jan/22 ] |
|
Attached you will find two documents produced by Thomas Trutt. One is a flowchart showing what happens at the circ desk and the other contains use cases. The Circulation POs will review the documents at their meeting on January 18, in preparation for the prior to the RA SIG meeting on January 18, in preparation for the RA SIG meeting on January 24. |