Inventory (UXPROD-785)

[UXPROD-492] Analyse and implement container object in Inventory Created: 06/Apr/18  Updated: 06/Dec/23

Status: In Refinement
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Inventory

Type: New Feature Priority: P3
Reporter: Charlotte Whitt Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: crossrmapps, inventory, metadatamanagement, po-mvp, round_iv
Remaining Estimate: Not Specified
Time Spent: 1 hour, 45 minutes
Original estimate: Not Specified

Attachments: PNG File Inventory Container record.png     PNG File Skärmavbild 2019-08-08 kl. 14.44.20.png     PNG File Skærmbillede 2018-11-06 kl. 00.06.11.png    
Issue links:
Blocks
blocks UIIN-300 Filter on record type (Instance, Cont... Open
blocks UXPROD-1298 Inventory App: Container Record: KB u... Blocked
blocks MODINV-351 Inventory App: Assign tags to contai... Blocked
blocks MODINVSTOR-597 Inventory App: Assign tags to contain... Blocked
blocks UIIN-310 Assign tags to Inventory Containers Blocked
blocks UIIN-495 Implement the general note/comment ap... Blocked
blocks UIIN-1304 Filter Container records by tags Blocked
blocks UXPROD-1105 Create Container record in inventory ... Blocked
blocks UXPROD-2769 Ability to tag Inventory Container re... Blocked
Defines
is defined by UIIN-155 Representation of package entity in I... In Progress
is defined by UIIN-695 SPIKE: Container in Inventory Draft
Gantt End to Start
has to be done before UXPROD-139 Avoid creation of duplicative metadat... Draft
Relates
relates to MODINVSTOR-111 Add Package entity to inventory Closed
relates to UX-273 New icon for container records in Inv... Closed
relates to UIIN-463 Container Record. Accordion Administr... Open
relates to UIIN-464 Container Record. Accordion Contained... Open
relates to UIIN-465 Container Record. Accordion Descripti... Open
relates to UIIN-466 Container Record. Accordion Identifie... Open
relates to UIIN-468 Container Record. Accordion Title dat... Open
relates to UIIN-469 Create container record with accordio... Open
relates to UIIN-489 Container Record. Accordion Descripti... Open
relates to UXPROD-138 Locally-stored metadata records for e... Closed
relates to UXPROD-1080 Locally-stored metadata records for e... Closed
relates to UIIN-467 Container Record. Accordion Container... Draft
relates to UIIN-473 Result list. Add icon for container r... Blocked
Potential Workaround: CW: Do dummy records!
Epic Link: Inventory
Analysis Estimate: Medium < 5 days
Analysis Estimator: Charlotte Whitt
Front End Estimate: XL < 15 days
Front End Estimator: Niels Erik Nielsen
Front-End Confidence factor: Medium
Back End Estimate: Large < 10 days
Back End Estimator: Niels Erik Nielsen
PO Rank: 104
PO Ranking Note: 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://folio-org.atlassian.net/wiki/pages/viewpage.action?pageId=5854462

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:



 Comments   
Comment by Cate Boerema (Inactive) [ 24/Sep/18 ]

I added "(container)" to the title of this feature. I also marked this as a blocker for UXPROD-1105 Blocked (Create Container record in inventory from PO Line).

Charlotte Whitt, is this really "analysis complete"? I only see one user story here ( UIIN-155 In Progress ) which seems to be kind of a design spike. Analysis complete means that all user stories and mockups are completed. See the definition of the status values in UXPROD here: https://folio-org.atlassian.net/wiki/display/COMMUNITY/Getting+Started+for+Product+Owners#GettingStartedforProductOwners-UXPRODEpicandFeatureWorkflow/Status

Thanks!

Comment by Charlotte Whitt [ 24/Sep/18 ]

Cate Boerema, we have the data elements - https://docs.google.com/spreadsheets/d/1RCZyXUA5rK47wZqfFPbiRM0xnw8WnMCcmlttT7B3VlI/edit#gid=163842260
And I'll do a UX detail view quite similar to detail view of the instance record (but this is not done yet!) – my plan is to get it done hopefully later this week.

But I can change the status - np

Comment by Cate Boerema (Inactive) [ 05/Dec/18 ]

Removing Q1 2019 fix version due to limited capacity in Q1 2019.

Comment by Kristin Martin [ 16/Apr/19 ]

Are there issues around delaying development of containers related to migration and connections between acquisitions data and inventory. Three user stories:
1. I want to associate a Purchase Order with a particular membership and understand all of the individual titles that are received as part of that membership.
2. I want to associate a purchase order for a group of titles (e.g., a print and online version of a serial or an mini-bundle of 2-3 titles) and have the acquisitions data apply to all titles.
3. I want to associate a purchase order with a monographic series (e.g., monographic series classified separately) and know what individual titles are received as part of the series. Because the individual volumes are cataloged and classified separately, they are not associated with the same inventory record.

Comment by Dennis Bridges [ 19/Jul/19 ]

Kristin Martin From the acquisitions perspective the container is essentially step 3. First we need to be able to use the POL to order a package of titles and Receive those titles (AKA check-in multiple titles against a POL). Step 2 is the connection with inventory and we have already built the ability to generate instances holdings and items based on a POL and its 'physical', 'electronic' or 'other' piece records (We need to build in how a POL generates multiple instances but the design is already complete). Step 3 would be allowing the user to choose to have the POL represented directly in inventory by a container, generating that container and associating it with the titles the POL has been connected to.

By the end of step 2 you will be able to accomplish all of three of the bullets listed above. The container may enhance visibility and provide additional functionality but the relationship between POL and multiple titles is the immediate priority for orders and receiving.

Comment by Felix Hemme [ 27/Sep/19 ]

Modeled workflows with and without container record: https://docs.google.com/document/d/1r7olPeix2TaS-ZXJZtoW4a7w_-Qo79NancIV0LdlBXc/edit?usp=sharing

Comment by Charlotte Whitt [ 13/Jan/20 ]

Hi Holly Mistlebauer - I noticed that UXPROD-1105 Blocked now has fix version as Q4 2020. Do that imply that we then set UXPROD-492 In Refinement , and if not doing the full data set, then the minimized data set ( UIIN-695 Draft ) as Q3 2020, so Inventory work is ready for Orders to build upon?

CC: Dennis Bridges

Comment by Dennis Bridges [ 13/Jan/20 ]

I think UXPROD-1105 Blocked should not be the issue that sets the priority for the Inventory feature. If the folks working on the inventory app decide that UXPROD-492 In Refinement is a priority it should be implemented accordingly. Once it has been implemented we can worry about UXPROD-1105 Blocked . My logic here is that creating the record from an order should be secondary to what the inventory app decides is best for the usability and functionality of inventory app. If and when things change in inventory acquisitions folks will revisit the question of how best to leverage the inventory app to enhance the workflow of acquiring material. Know what I mean?Just my two cents

Comment by Jacquie Samples [ 23/Sep/20 ]

I agree with Dennis that creating dummy records as a work-around is not sustainable and will cause problems later when the needed features listed here are developed. It appears that the high ranking supports Dennis's 2 cents.

Generated at Fri Feb 09 00:08:21 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.