Inventory
(UXPROD-785)
|
|
| 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: |
|
||||||||||||||||
| Issue links: |
|
||||||||||||||||
| 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:
This change might need to be coordinated with having the UI made customizable. Tasks: |
| Comments |
| Comment by Charlotte Whitt [ 09/Dec/19 ] |
|
Thread on Slack 12/9/2019: Andrea Loigman Marc Johnson Andrea Loigman |
| 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 ] |
This will effectively make the field optional from an API perspective, as the API can only express the weakest of the constraints |