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

Inventory. Item record. Make item material type optional

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Epic Link:
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      2
    • PO Rank:
      31
    • Rank: Chalmers (Impl Aut 2019):
      R5
    • Rank: Chicago (MVP Sum 2020):
      R4
    • Rank: Cornell (Full Sum 2021):
      R5
    • Rank: Duke (Full Sum 2021):
      R5
    • Rank: 5Colleges (Full Jul 2021):
      R5
    • Rank: GBV (MVP Sum 2020):
      R5
    • Rank: Grand Valley (Full Sum 2021):
      R4
    • Rank: hbz (TBD):
      R5
    • Rank: MO State (MVP June 2020):
      R5
    • Rank: TAMU (MVP Jan 2021):
      R5
    • Rank: U of AL (MVP Oct 2020):
      R5

      Description

      Overview: As an overall principle then data elements in Inventory is implemented as non required elements to accommodate most possible flexibility. Today we only have a few required elements the current implementation, and item material type is one of these required elements, while it's used in the loan rules editor, and in the UI display. From some early implementer libraries it has been raised a proposal to change item material type to be an optional element.

      The element Material type in the Item record, has been defined as a Required, Not repeatable element, while it has been associated with loan rules, display in result list etc. The current solution have lately been evaluated, and the MM-SIG plan to initiate a review/discussion at the upcoming WolfCon meeting in January 2020.

      This change would require:

      1. analyze technical aspects of this change and solutions
      2. rethink the UI display where we use Item material type

      This change might need to be coordinated with having the UI made customizable.

      Tasks:
      1) At WolfCon discuss/review our current implementation having the Material type in the Item record, being a Required, Not repeatable element
      2) Analyze the impact on other apps when changing the element Material type to be: Not required, repeatable
      3) Decide to implement this (knowing this is a breaking change in the back end) - POST MVP.

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                charlotte Charlotte Whitt
                Reporter:
                charlotte Charlotte Whitt
                Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases