Loans (UXPROD-788)

[UXPROD-246] Confirm checkin/checkout windows based on item characteristics (multipiece, suppressed in Inventory) Created: 21/Feb/18  Updated: 16/Sep/20  Resolved: 04/Feb/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q1 2019
Parent: Loans

Type: New Feature Priority: P3
Reporter: Darcy Branchini Assignee: Emma Boettcher
Resolution: Done Votes: 0
Labels: check-in, loans, resourceaccess
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by UXPROD-124 Analyse and implement 'missing' eleme... Closed
Cloners
is cloned by UXPROD-1330 Display checkin notes from Inventory ... Closed
Relates
relates to UICHKIN-42 Display modal when item not found Closed
relates to UX-185 Create mock-up for item not found at ... Closed
relates to UX-195 Check in alert modal - multipiece item Closed
relates to UICHKIN-46 Check in: Display modal for multipiec... Closed
relates to UICHKOUT-446 Check out: Display modal for multipie... Closed
Epic Link: Loans
Analysis Estimator: Darcy Branchini
Front End Estimate: Small < 3 days
Front End Estimator: Jakub Skoczen
Back End Estimator: Jakub Skoczen
Estimation Notes and Assumptions: Backend estimate assumes that these modals are displayed prior to performing a check in or check out in the API, and that all of the relevant item properties already exist.

For modal development only, actions that require additional screens are not factored in this.
Development Team: Prokopovych
Rank: BNCF (MVP Feb 2020): R1
Rank: Chalmers (Impl Aut 2019): R1
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: GBV (MVP Sum 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

Information about an item may inform whether or not the user should check it in or out. User should be able to exit the confirmation window without completing the interaction.

  • Multipiece items
  • Suppressed items (at holding, instance or item level)
    • based on SIG conversations 12/17, there is no need to have alerts especially for suppressed items, but this information may be necessary for other workflows (checking in Missing items, checking in Lost items).

An alert should also display in the checkin/checkout apps when the item's barcode is not found in Inventory.

Out of scope:
Other notes previously referenced on this page (https://docs.google.com/spreadsheets/d/13jdIOnNJkljNn22Jykbd7bmxYVM2QXmbKtbd1LJuu1E/edit#gid=0) have been moved to their own features.

  • UXPROD-601 Closed covers in transit to home location
  • Requests epic covers any alerts needed for checking in requested items
  • UXPROD-1330 Closed covers manual checkin notes entered in Inventory
  • Alerts that an item is in a particular state (e.g., Missing) have been moved to the features for that state
  • Fast add states ( UXPROD-1352 Blocked )
  • Item is in special location ( UXPROD-1353 Draft )


 Comments   
Comment by Cate Boerema (Inactive) [ 27/Sep/18 ]

Hi Emma. I think this feature might be too big/have too many dependencies to naturally fit within any given quarter.

Perhaps, alternatively, the check-in modal window stories should be part of the features that generate them. For example, we could move the story for the "Item is returned and is housed at another library" ( UICHKIN-41 Closed ) modal to the "In transit to home location (not to fulfill request)" ( UXPROD-601 Closed ) feature.

If we want to keep this JIRA issues as a kind of umbrella, we could convert it to an Umbrella and put it in the FOLIO project. Thoughts?

Comment by Emma Boettcher [ 27/Sep/18 ]

Most of these windows do have related features, so that's not a problem. The ones I would have trouble finding a place for are the Item not Found & Multipiece items - would it make more sense for them to be split out as their own features?

Comment by Cate Boerema (Inactive) [ 12/Oct/18 ]

Thanks for moving many of these to their related features!

Most of these windows do have related features, so that's not a problem. The ones I would have trouble finding a place for are the Item not Found & Multipiece items - would it make more sense for them to be split out as their own features?

If you can cleanly break this into just a couple features, that would be great, but, given the number of remaining modals specified above, breaking these all out into different features seems like it might be a lot. I am okay with leaving this as a kind of catch-all for now.

Comment by Theodor Tolstoy (One-Group.se) [ 07/Nov/18 ]

Hi Emma Boettcher, For Go live, Chalmers would need some, but not all of these features. Would it be possible to split this up?

Do you want to meet with Chalmers in order to see which ones they need? I could facilitate for that.

Comment by Emma Boettcher [ 07/Nov/18 ]

Theodor Tolstoy (One-Group.se) Yes, I think splitting it up would be a good idea, and meeting to figure out which ones are most important is also a good plan.

Comment by Marc Johnson [ 04/Dec/18 ]

Cate Boerema Jakub Skoczen Similarly to my question on UXPROD-1330 Closed . Given the recent conversations we had about only presenting information in the check in / check out UI, prior to actioning that in the API. Can we assume that this is only presentation of information to the staff member about the item?

Does this include blocking suppressed items from being checked out in the backend API?

Comment by Cate Boerema (Inactive) [ 04/Dec/18 ]

I think it's just informational, but Emma Boettcher would know best.

Comment by Cate Boerema (Inactive) [ 13/Dec/18 ]

Hi Marc Johnson. Emma Boettcher answered your above question in the comments on UXPROD-1330 Closed . Can you please adjust the backend estimate on this, if applicable?

Copied from the comments in the other issue:

Marc Johnson Cate Boerema The presence of these notes doesn't block checkin outright, but the staff user, upon seeing the information in them, may want to stop the checkin. (Similar to a multipiece item, as in UXPROD-246 Closed ). If I'm understanding the terms Marc's using correctly, it presents information about the items, and then if the user confirms, starts the process.

Comment by Marc Johnson [ 18/Dec/18 ]

Cate Boerema I've updated the backend estimate based upon Emma Boettcher comments

Comment by Cate Boerema (Inactive) [ 02/Jan/19 ]

Thanks Marc Johnson. So there's really 0 back end for this? If so, that will really help us get our Q1 deliverables done

Comment by Marc Johnson [ 02/Jan/19 ]

Cate Boerema Yes, I believe that there is no backend work for this

Comment by Cate Boerema (Inactive) [ 29/Jan/19 ]

Emma Boettcher is the work for this feature now complete? If so, can you please close it?

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