Inventory (UXPROD-785)

[UXPROD-2178] Inventory. Item record. Make item material type optional Created: 04/Dec/19  Updated: 18/Dec/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: TBD
Parent: Inventory

Type: New Feature Priority: P3
Reporter: Charlotte Whitt Assignee: Ryan Taylor
Resolution: Unresolved Votes: 0
Labels: back-end, epam-folijet, inventory, metadatamanagement, post-mvp, resourceaccess, ui-inventory
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Skärmavbild 2019-12-04 kl. 11.50.33.png     PNG File Skärmavbild 2019-12-04 kl. 11.51.38.png     PNG File Skärmavbild 2019-12-04 kl. 11.52.22.png    
Issue links:
Defines
defines UXPROD-785 Inventory In Progress
Relates
relates to UXPROD-2211 Custom Fields in Inventory Draft
Release: Not Scheduled
Epic Link: Inventory
Development Team: Folijet
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   

Discuss with all item record stakeholder POs before moving forward

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.



 Comments   
Comment by Charlotte Whitt [ 09/Dec/19 ]

Thread on Slack 12/9/2019:

Andrea Loigman
@charlotte @cate I'm not sure that making material type optional is a wise choice. In fact depending on how it effects circulation rule behavior it could be a very choice.

Marc Johnson
I think it’s worth asking the question “how do we want organisations that don’t use material types to experience the system?”

Andrea Loigman
Have a default material type of nil.
But for those of us that have many material types (and that will be by far the larger number of institutions), having rules that could bypass material type as a criteria and behave universally would be awful. Especially with the limited hierarchy of location and the current non-functionality of the value pairs that were supposed to replace additional layers. Material type is the only way any of that can be controlled for now.

Comment by Andrea Loigman [ 10/Feb/20 ]

My understanding of the outcome at WOLFcon was that we'd eventually like required/not required to be set at the tenant level for this field.

Comment by Marc Johnson [ 11/Feb/20 ]

we'd eventually like required/not required to be set at the tenant level for this field

This will effectively make the field optional from an API perspective, as the API can only express the weakest of the constraints

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