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

NFR: Using reference records for item status

    XMLWordPrintable

Details

    • New Feature
    • Status: Draft (View Workflow)
    • TBD
    • Resolution: Unresolved
    • None
    • None
    • None
    • None
    • Hide
      This would require changing representation of an item status.

      It would also need decisions about how to refer to item statuses within the system, e.g. how does another module know that 12345 = checked out, and that this status exists for this tenant

      The estimate reflects that there are technical decisions to be made, as well as significant impact on modules across the system (e.g. circulation, maybe acquisitions, data import etc)
      Show
      This would require changing representation of an item status. It would also need decisions about how to refer to item statuses within the system, e.g. how does another module know that 12345 = checked out, and that this status exists for this tenant The estimate reflects that there are technical decisions to be made, as well as significant impact on modules across the system (e.g. circulation, maybe acquisitions, data import etc)
    • 93.3
    • R4
    • R4
    • R4
    • R1
    • R2
    • R4
    • R2
    • R2
    • R1
    • R2
    • R1
    • R2

    Description

      Currently item status is restricted to a list of values as specified in the item JSON schema:
      https://github.com/folio-org/mod-inventory-storage/blob/master/ramls/item.json

      In order to continue development on the item state feature, we need to create reference records for item status instead of using the hard-coded values in the schema. This is needed to support adding additional configuration values, support custom item statuses, and potentially to support translation workflows.

      While this jira is currently assigned to Prokopoych, the needed work spans multiple modules and multiple development teams, so the description here is meant to start drafting the needs in one place, and then it can start to be split apart into multiple features.

      Considerations

      A longer document outlining feature needs and scope is in the FOLIO wiki at
      https://wiki.folio.org/display/AppInt/Item+Status+as+Reference+Records+-+UXPROD-1927

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                enettifee Erin Nettifee
                ecboettcher Emma Boettcher
                Marc Johnson Marc Johnson
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:

                  TestRail: Runs

                    TestRail: Cases