Receiving functionality that FOLIO needs to stay competitive
(UXPROD-3438)
|
|
| Status: | In Refinement |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Receiving functionality that FOLIO needs to stay competitive |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Cate Boerema (Inactive) | Assignee: | Dennis Bridges |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | acq-morningglory-candidate, acquisitions, cornell-priority, receiving, round_iv | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||
| Epic Link: | Receiving functionality that FOLIO needs to stay competitive | ||||||||||||||||||||||||
| Front End Estimate: | Medium < 5 days | ||||||||||||||||||||||||
| Front-End Confidence factor: | Low | ||||||||||||||||||||||||
| Back End Estimate: | Medium < 5 days | ||||||||||||||||||||||||
| Development Team: | Thunderjet | ||||||||||||||||||||||||
| Kiwi Planning Points (DO NOT CHANGE): | 55 | ||||||||||||||||||||||||
| PO Rank: | 84 | ||||||||||||||||||||||||
| Rank: Chalmers (Impl Aut 2019): | R4 | ||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R5 | ||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R1 | ||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R4 | ||||||||||||||||||||||||
| Rank: FLO (MVP Sum 2020): | R4 | ||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R1 | ||||||||||||||||||||||||
| Rank: hbz (TBD): | R2 | ||||||||||||||||||||||||
| Rank: Hungary (MVP End 2020): | R1 | ||||||||||||||||||||||||
| Rank: Lehigh (MVP Summer 2020): | R4 | ||||||||||||||||||||||||
| Rank: Leipzig (Full TBD): | R1 | ||||||||||||||||||||||||
| Rank: Mainz (Full TBD): | R1 | ||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R4 | ||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R2 | ||||||||||||||||||||||||
| Rank: Trinity College (Jun 2021): | R3 | ||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R4 | ||||||||||||||||||||||||
| Description |
|
Problem: User has to add each expected piece individually. Pieces are added almost daily while ordering is active and this can consume a significant amount of time. Patterns might also trigger automated claiming when an issue is overdue High level requirements:
Workflow mockups: https://drive.google.com/drive/folders/1EDEZAWpteiV-NZc_W9sjfTWlr4bpmd7N?usp=sharing Note there are standards for identifying publication patterns defined in MARC. These should be considered in order to improve the transferability of data to and from FOLIO. https://www.itsmarc.com/crs/mergedProjects/holdings/holdings/idh_853_855_hold.htm |
| Comments |
| Comment by Kristin Martin [ 18/Apr/19 ] |
|
Can we clarify--is this referring specifically and exclusively to patterns? If so, Chicago does not need this. |
| Comment by Dennis Bridges [ 18/Apr/19 ] |
|
Kristin Martinyes this is specifically in reference to creating and managing checkin patterns. |
| Comment by Kristin Martin [ 19/Apr/19 ] |
|
What is the status of predictive check-in? We are not doing predictive check-in, so I'm not advocating for it, but we didn't see it represented in other feature tickets and would just like to know. |
| Comment by Dennis Bridges [ 23/Apr/19 ] |
|
Kristin Martin There is still interest in providing predictive checkin functionality but on account of the priorities identified by the community conversations have been focused elsewhere. The original analysis resulted in the attached mockup but hasn't been refined since... |
| Comment by Lisa Sjögren [ 16/Aug/19 ] |
|
Hi Dennis Bridges! |
| Comment by Dennis Bridges [ 19/Aug/19 ] |
|
Hi Lisa Sjögren there is a story for editing expected receipt date on a piece by piece basis but it is related to
|
| Comment by Lisa Smith [ 03/Jun/22 ] |
|
Have predictive abilities sounds like a time saver for creating future pieces as part of the check-in steps. Anything that reduces keystrokes and clicks would be good! |