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

Analyse and implement container object in Inventory

    XMLWordPrintable

    Details

    • Template:
    • Potential Workaround:
      CW: Do dummy records!
    • Epic Link:
    • Analysis Estimate:
      Medium < 5 days
    • Front End Estimate:
      XL < 15 days
    • Back End Estimate:
      Large < 10 days
    • Confidence factor:
      Medium
    • Development Team:
      Prokopovych
    • Calculated Total Rank:
      82
    • PO Rank:
      104
    • PO Ranking Note:
      Hide
      CW: The feature for the Order app creating container records (UXPROD-1105) has the calculated institutional ranking: 110, PO ranking: 76). The Order feature is dependent on having the container in Inventory.
      DB: Just clarifying here. UXPROD-1105 is for the creation of the container based on a POL. Which of course, relies on the container being possible to create. However, this is currently related to receiving packages (UXPROD-1547) but not required. Someone could receive packages of material through checkin using instances as a workaround.
      Show
      CW: The feature for the Order app creating container records ( UXPROD-1105 ) has the calculated institutional ranking: 110, PO ranking: 76). The Order feature is dependent on having the container in Inventory. DB: Just clarifying here. UXPROD-1105 is for the creation of the container based on a POL. Which of course, relies on the container being possible to create. However, this is currently related to receiving packages ( UXPROD-1547 ) but not required. Someone could receive packages of material through checkin using instances as a workaround.
    • Rank: Chalmers (Impl Aut 2019):
      R5
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R4
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: FLO (MVP Sum 2020):
      R2
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: hbz (TBD):
      R1
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R4
    • Rank: Leipzig (Full TBD):
      R1
    • Rank: Leipzig (ERM Aut 2019):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R5

      Description

      Analyse and possible implement the container object described in The Codex Metadata Model - https://wiki.folio.org/pages/viewpage.action?pageId=1415393

      Local package is part of the initial model - which consists of 5 objects: package, instance, item/holding/coverage, and location. Vince's model is inspired by BIBFRAME2, but the Package object in this model is new, and does not originate from BIBFRAME.

      At MM-SIG meeting on 4/5/2018:
      The role of a package structure in inventory. Some options:

      • Instance records could represent packages in inventory
      • There could be a package structure in inventory, instead of a package becoming an instance. This could be a new entity within inventory.

      UX-mock up - reviewed by the Container Small Group on 8/8/2019:

      Documents:

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                charlotte Charlotte Whitt
                Reporter:
                charlotte Charlotte Whitt
                Analysis Estimator:
                Charlotte Whitt Charlotte Whitt
                Front End Estimator:
                Niels Erik Gilvad Nielsen Niels Erik Gilvad Nielsen
                Back End Estimator:
                Niels Erik Gilvad Nielsen Niels Erik Gilvad Nielsen
                Votes:
                0 Vote for this issue
                Watchers:
                14 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 1 hour, 45 minutes
                    1h 45m

                      TestRail: Runs

                        TestRail: Cases