Receiving functionality that FOLIO needs to stay competitive (UXPROD-3438)

[UXPROD-194] Checkin Maintenance (managing pieces with publication patterns) Created: 20/Jan/18  Updated: 05/Oct/22

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:
Relates
relates to UXPROD-3438 Receiving functionality that FOLIO ne... In Progress
relates to UXPROD-2373 Allow for the display of piece inform... Closed
relates to UIOR-253 Create expected check-in pieces autom... Draft
relates to UIOR-254 Create Expected check-in piece based ... Draft
relates to UXPROD-1845 Claiming unreceived or unreceivable i... Analysis Complete
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:

  • Allow the user to add pieces based on a pattern that will create pieces with different captions and expected receipt dates as defined (also known as predictive checkin)
  • Allow the user to adjust the pattern of expected pieces and have the pieces that have been created update to align with adjustments made to the pattern
  • Would be good to have default patterns or be able to share patterns across libraries (some published long ago by Library of Congress may still be available); large libraries being able to share patterns across the community would be really helpful, so that each library does not have to create all of them on their own

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.
If this has to do with being to edit what we are receiving, we need to this at go-live.

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...
Unable to render embedded object: File (Screen Shot 2019-04-23 at 9.44.10 AM.png) not found.

Comment by Lisa Sjögren [ 16/Aug/19 ]

Hi Dennis Bridges!
Does this feature represent the only currently planned(ish) way of being able to add a date by which individual pieces are expected, or is there another feature for adding dates manually to each piece as you create it? Or one for creating - rather than adjusting - a pattern?

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 UXPROD-1547 Closed . However, this particular feature should cover both the creation and adjustment of patterns for expected pieces. I will update the description to clarify this.

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!

Generated at Fri Feb 09 00:06:27 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.