Item states (status) (UXPROD-1321)

[UXPROD-1590] Implement Process in the Three-Part Item State Created: 15/Mar/19  Updated: 08/Feb/24

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Item states (status)

Type: New Feature Priority: TBD
Reporter: Emma Boettcher Assignee: Thomas Trutt
Resolution: Unresolved Votes: 0
Labels: po-mvp, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File uxprod-1530,1590-edit-item-record.png     PNG File uxprod-1530,1590-settings.png     PNG File uxprod-1530,1590-view-item-record-1.png     PNG File uxprod-1530,1590-view-item-record-2.png    
Issue links:
Blocks
blocks UXPROD-1622 Bulk manipulation of item state for s... Closed
blocks UXPROD-1352 Item status: Set Needed for and/or Pr... Blocked
Cloners
clones UXPROD-1530 Implement Needed for in the Three-Par... Draft
Defines
is defined by CIRC-1641 Add "Process" to items-in-transit report Draft
is defined by CIRC-1643 Add "Process" to hold shelf clearance... Draft
is defined by UX-374 Mockups for view, edit item record wi... Draft
is defined by UX-375 Mockups for 3-part item state settings Draft
Duplicate
duplicates UXPROD-1037 Item state in three components Closed
Potential Workaround: Checking out items to dummy patrons or using item notes while an item has the In process status.
Epic Link: Item states (status)
Front End Estimate: XL < 15 days
Front End Estimator: Michal Kuklis
Front-End Confidence factor: Low
Back End Estimate: XXL < 30 days
Back End Estimator: Marc Johnson
Development Team: Prokopovych
PO Rank: 97
PO Ranking Note: Not all schools have ranked this feature, but analogous features exist in other systems, likely making it go-live for schools who are using those systems.
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R4
Rank: FLO (MVP Sum 2020): R2
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R2
Rank: MO State (MVP June 2020): R2
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R4

 Description   

Current situation or problem:
FOLIO currently has no way to show which process an item is in. An item can have its item status set to In process, but there is no information about which staff are working with the item.

Users could work around this by using statistical codes or dummy patrons, but the latter is untenable because it generates fines/notices/statistics that are a headache to clean up.

In scope

  • Allow users to configure values for a process an item can be in (these can also be used values in a set of processes the item is needed for, UXPROD-1530 Draft )
  • Allow a user to assign one of those values to an item, and to add notes when assigning those values
    • while editing item record in Inventory
  • Allow a user to remove that value from an item
  • Display of those values when item displays across different apps
  • logic at Check In
    • Settings to configure whether user has to confirm check in if item has a value for Process
      • Eventually, should be able to configure this per value for Process
    • if so configured in settings, ask user to confirm check in when an item has a value for process
    • when item is checked in with a value for process, remove the value for process

Out of scope

  • Bulk editing this field (should be included in bulk edit feature)
  • Any use of the process field in circulation rules or circulation policies.

Use case(s)

  • A library sends a set of items to an external firm for binding and/or physical repair.
  • A library sends an item to in-house preservation staff for physical repair / boxing.
  • A library puts an item into cold storage as part of disaster response protocols.
  • A library is digitizing an item in order to place a digital copy into an online digital collection.
  • A library is digitizing an item in order to have a digital copy for use with controlled digital lending.
  • A library staff member is doing original cataloging of the item.
  • A library has sent the item to an external firm for cataloging.
  • An item is being prepared for, or is currently on, exhibit.
  • An item is being prepared for being placed on reserve for a course.
  • An item is being moved into a temporary themed collection.

Proposed solution/stories

  • General development approach
    • Settings page
    • Inventory
      • Item updates ( UX-374 Draft )
      • Search filters
      • Instance display (holdings accordion)
    • Request whitelist behavior - hold, page, recall
    • Check in behavior - allow, allow/warn, prohibit
    • Check out behavior - allow, allow/warn, prohibit
    • Inventory search
    • Data import behavior
    • Data export behavior
    • Bulk edit behavior
    • Circ log updates - new events to capture, new filters, update existing filters
    • Canned reports
      • in transit items (inventory)
      • overdue loans, claim returned, cash drawer reconciliation, financial detail, refunds to process manually (users), hold shelf clearance (requests)

Links to additional info

Questions



 Comments   
Comment by Erin Nettifee [ 09/Jul/19 ]

This and UXPROD-1530 Draft were discussed at the RA SIG meeting, with the idea of defining a full feature set, and then a UXPROD with a "thin-thread" version of the implementation of staff workflow functionality for "needed for" and Process. Once that "thin thread" UXPROD is defined out, Duke can re-evaluate 1530 and 1590 to see if we can downgrade from go-live.

Comment by David Bottorff [ 09/Jul/19 ]

Same for Chicago. This should remain go-live if this is where the "thin thread" version will live. If the UXPROD for the thin thread for this and UXPROD-1530 Draft are split off, then we can downgrade this. Chicago only needs the thin thread for both at go-live.

Comment by Emma Boettcher [ 01/Oct/20 ]

Marc Johnson and Michal Kuklis I know you estimated this over a year ago, and there's been more concrete discussions on requirements for this feature since then. Could you review your estimates to see if they're still the same, or let me know if you have questions?

Comment by Michal Kuklis [ 01/Oct/20 ]

Emma Boettcher I think I would change it to XXL after reviewing this a bit closer. I have one question for you. Where would we fit "Tracking status history" from slide 15?

Comment by Emma Boettcher [ 01/Oct/20 ]

Michal Kuklis that's a different feature - UXPROD-2175 Open .

Comment by Emma Boettcher [ 02/Oct/20 ]

Bohdan Suprun I'm trying to get estimates for my features before the cap-planning deadline on Monday. Since Marc is out, could you estimate the backend for this? The previous estimate is older, and now that the feature is more detailed I'm wondering if the estimate would be the same. Please let me know if you have questions.

Comment by Bohdan Suprun (Inactive) [ 02/Oct/20 ]

Emma Boettcher,

It still a big feature, at least 20 days are required. We have to build new API, update item with the new properties, forward the properties from storage everywhere this properties should be displayed.

I'll leave Marc's estimation.

Comment by Marc Johnson [ 06/Oct/20 ]

Emma Boettcher Bohdan Suprun

It still a big feature, at least 20 days are required. We have to build new API, update item with the new properties, forward the properties from storage everywhere this properties should be displayed.

I agree.

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