Requests
(UXPROD-790)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Requests |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Cate Boerema (Inactive) | Assignee: | Cate Boerema (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | appreport, po-mvp, requests | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||
| Potential Workaround: | Cate Boerema: There is no workaround for this report using the current Requests app or Requests csv. Most on SIG feel strongly that we need at least a thin thread implementation for mvp. Erin Nettifee investigating whether this info would be available in the LDP. If not, we probably need to add at least the following to the requests csv: Status update date, Service point to, Service point from. | ||||||||||||||||||||||||
| Epic Link: | Requests | ||||||||||||||||||||||||
| Analysis Estimate: | Medium < 5 days | ||||||||||||||||||||||||
| Analysis Estimator: | Tania Fersenheim | ||||||||||||||||||||||||
| Front End Estimate: | Medium < 5 days | ||||||||||||||||||||||||
| Front End Estimator: | Tania Fersenheim | ||||||||||||||||||||||||
| Front-End Confidence factor: | Low | ||||||||||||||||||||||||
| Back End Estimate: | XL < 15 days | ||||||||||||||||||||||||
| Back End Estimator: | Tania Fersenheim | ||||||||||||||||||||||||
| Estimation Notes and Assumptions: | estimates based on other appreport features | ||||||||||||||||||||||||
| Development Team: | Prokopovych | ||||||||||||||||||||||||
| PO Rank: | 96 | ||||||||||||||||||||||||
| PO Ranking Note: | 2019-07-18: Bumping PO rank per discussion with SIG. This seems higher priority than default pickup service point for users
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): | R4 | ||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R1 | ||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R2 | ||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||||||||||
| Rank: FLO (MVP Sum 2020): | R2 | ||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R2 | ||||||||||||||||||||||||
| Rank: hbz (TBD): | R2 | ||||||||||||||||||||||||
| Rank: Hungary (MVP End 2020): | R1 | ||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R2 | ||||||||||||||||||||||||
| Rank: Leipzig (Full TBD): | R1 | ||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R1 | ||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R2 | ||||||||||||||||||||||||
| Description |
|
Purpose: Institutions that allow items to transit between service points to fill requests will want to run a report periodically - probably daily - that lists items that are in transit to or from a particular service point that should have arrived by now, based on expected transit times. The report must contain bib information, item call #, item barcode, etc as well as the service point an item is coming from, where it is going to, and when it became in transit. NOTE - The concept of "average travel time" between service points has been discussed in passing but not defined or analyzed. An expected transit time is probably needed for any time an item is travelling between service points, not just to fill a request. Some thin thread implementation ideas:
|
| Comments |
| Comment by Karen Newbery [ 26/Mar/19 ] |
|
It seems to me that this is a sub-set of the
|
| Comment by Tania Fersenheim [ 27/Mar/19 ] |
|
Karen Newbery -
|
| Comment by Anya [ 29/Mar/19 ] |
|
Comment from the March meeting : the ability to pull a CSV or get to the data is a must . |
| Comment by Erin Nettifee [ 24/Jul/19 ] |
|
I followed up on this with Duke's rep to the reporting SIG. We can expect that request and in-transit fields would be available in the LDP once a report is spec'd for the LDP that is using those fields. There is an existing report in the requested reports list - "Items in transit for too long" -
Because the Reporting SIG is in the middle of moving reports into UXPROD to be included in capacity planning, I don't know how we would know if this would be available for go-live. My sense is the thin-thread approach needs to move ahead, given the important of this for RA needs. |
| Comment by Cate Boerema (Inactive) [ 30/Jul/19 ] |
|
Thanks Erin Nettifee. I have marked this po-mvp based on SME feedback on its importance |
| Comment by Cate Boerema (Inactive) [ 11/Sep/19 ] |
|
Discussed this feature with the RA SIG on 2019-08-07. It turns out they really need a list of items in transit. There is a separate feature for this which Emma created (
|