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

Audit status changes and display in app (status history)

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Epic Link:
    • Front End Estimate:
      XXL < 30 days
    • Back End Estimate:
      XXL < 30 days
    • Estimation Notes and Assumptions:
      Hide
      It is needed to create a new UI app and cover the scope.

      Backend:
      Need to rethink the approach to do it on the backend as the existing similar approach for loan actions history is not considered a best practice and needs improvements
      Show
      It is needed to create a new UI app and cover the scope. Backend: Need to rethink the approach to do it on the backend as the existing similar approach for loan actions history is not considered a best practice and needs improvements
    • Development Team:
      Firebird
    • Calculated Total Rank:
      45
    • Kiwi Planning Points (DO NOT CHANGE):
      16
    • PO Rank:
      93.4
    • Rank: Chalmers (Impl Aut 2019):
      R2
    • Rank: Chicago (MVP Sum 2020):
      R2
    • Rank: Cornell (Full Sum 2021):
      R4
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R2
    • Rank: GBV (MVP Sum 2020):
      R4
    • Rank: hbz (TBD):
      R2
    • Rank: Lehigh (MVP Summer 2020):
      R2
    • Rank: MO State (MVP June 2020):
      R2
    • Rank: U of AL (MVP Oct 2020):
      R3

      Description

      Current situation or problem:
      FOLIO tracks an item's current item status and the date and time it changed to that item status, but there is no information available in the UI about previous item statuses. (Some information about whether an item has circulated is available through the circulation log.)

      In scope
      Every time status changes, capture:

      • item
      • status it changed from
      • status it changed to
      • when (date and time)
      • app (for context as to how status changed) (differentiate batch changes from individual changes)
      • user
      • user's service point, if applicable (helpful for consortia)

      Out of scope

      • Any other changes to item record (may be useful to capture at some point, but not as part of this story)
      • configuring whether the user changing the item status is captured or not (UXPROD-2467)

      Use case(s)

      Proposed solution/stories

      • Mod-audit was originally proposed as an implementation of this, but discussion hasn't proceeded since those stories were created.

      Links to additional info
      https://docs.google.com/spreadsheets/d/19_aA7bhRIxhcC6Gz-rK_LrfOtz8F5VaOmOcsFsdGU8I/edit#gid=1676679098

      Questions

      • Capture this along with all other changes to an item?
      • To what extent can this build on/reuse work from the circulation log?

      split from: UXPROD-283.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                charlotte Charlotte Whitt
                Reporter:
                ecboettcher Emma Boettcher
                Front End Estimator:
                Viktor Soroka Viktor Soroka
                Back End Estimator:
                Dmytro Popov Dmytro Popov
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases