Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-1622

Bulk manipulation of item state for staff workflow needs

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Blocked (View Workflow)
    • Priority: TBD
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
      UXPROD features
    • Epic Link:
    • Front End Estimate:
      XL < 15 days
    • Back End Estimate:
      XXL < 30 days
    • Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      Hide
      CB: Per discussion with Jakub and cap planning team, a few of us non-developers are going to estimate the remaining unestimated features so as not to disrupt development. I am giving this 15/30 (FE/BE) based on the estimates for UXPROD-1590. I'll tag this feature as "SWAG" so we know to come back to this when we have more info.
      Show
      CB: Per discussion with Jakub and cap planning team, a few of us non-developers are going to estimate the remaining unestimated features so as not to disrupt development. I am giving this 15/30 (FE/BE) based on the estimates for UXPROD-1590 . I'll tag this feature as "SWAG" so we know to come back to this when we have more info.
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      45
    • Kiwi Planning Points (DO NOT CHANGE):
      2
    • PO Rank:
      68
    • 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):
      R3
    • Rank: hbz (TBD):
      R4
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R2
    • Rank: MO State (MVP June 2020):
      R4
    • Rank: TAMU (MVP Jan 2021):
      R2
    • Rank: U of AL (MVP Oct 2020):
      R4

      Description

      Current situation or problem:
      When a bulk editing function is introduced to FOLIO, it should also include the ability to edit item status in bulk.

      Item status bulk edits can't be a free-for-all; certain restrictions should exist:

      • Can't change item status from Checked out, Declared lost, Claimed returned, Aged to lost, or On order
      • Can't change item status to Checked out, Declared lost, Claimed returned, Aged to lost, Awaiting pickup, or Awaiting delivery

      In scope

      • Restrict certain item status changes in bulk edit as they would be restricted when changing item status from the item record
      • Handle failures
      • Handle editing item status to be Available when there's a request on an item (should item status then be Paged?)

      Out of scope

      Use case(s)

      Proposed solution/stories

      Links to additional info
      From comments on UXPROD-1731: "Certain workflows also require setting of the item status at the point that an item is created or when it is updated, whether it is manual or in batch. For example, contract cataloging: when we send batches of titles out for cataloging, we may need to set the item status in batch and then again when we receive them back."
      https://wiki.folio.org/display/AppInt/Item+status+%28item+state%29+subgroup

      Questions

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Unassigned Unassigned
                Reporter:
                ecboettcher Emma Boettcher
                Front End Estimator:
                Cate Boerema Cate Boerema
                Back End Estimator:
                Cate Boerema Cate Boerema
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases