Ordering functionality that FOLIO needs to stay competitive (UXPROD-3440)

[UXPROD-2455] Add a configurable, independent 'order material type' field to POL Created: 09/Jun/20  Updated: 09/Dec/21

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Ordering functionality that FOLIO needs to stay competitive

Type: New Feature Priority: P4
Reporter: Dennis Bridges Assignee: Dennis Bridges
Resolution: Unresolved Votes: 0
Labels: acquisitions, needs-ranking, orders, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Creat-edit order material type.png     PNG File Edit Screen Shot 2020-06-09 at 3.41.35 PM.png     PNG File View Screen Shot 2020-06-09 at 3.43.30 PM.png     PNG File View entries Screen Shot 2020-06-09 at 3.50.08 PM.png    
Issue links:
Cloners
clones UXPROD-1025 Ability to configure an ACQ specific ... Closed
Relates
relates to UXPROD-2255 RM-Costs Cluster Open
relates to UXPROD-2368 ERM-Agreements Costs Cluster Closed
relates to UXPROD-2408 ERM-Inventory Costs Cluster Closed
relates to UXPROD-1141 Create, close, cancel, Purchase Orders Closed
Epic Link: Ordering functionality that FOLIO needs to stay competitive
Front End Estimate: Medium < 5 days
Front-End Confidence factor: Medium
Back End Estimate: Medium < 5 days
Development Team: Thunderjet
Kiwi Planning Points (DO NOT CHANGE): 1
PO Rank: 59.5
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R3
Rank: GBV (MVP Sum 2020): R1
Rank: Grand Valley (Full Sum 2021): R3
Rank: MI State-Lib of MI (Sum 2021): R3
Rank: MO State (MVP June 2020): R4
Rank: TAMU (MVP Jan 2021): R3
Rank: U of AL (MVP Oct 2020): R2

 Description   

Purpose:

User needs the ability to customize their list of material types specific to orders and order lines for accurate tracking and reporting on order activity. These material types will not be an accurate reflection of the variety of individual items that may be acquired via this purchase order.

In addition to having the separate list, RM SIG wants to be able to set a default item material type from the Orders perspective, so that when an Order is set to create an item record, they don’t have to set the material type at that point.

Use case:

  • Use a default item material type of “On Order” or “Pending” to signal that the real item material type value had not yet been set. Libraries would not HAVE to do that if they don’t want to.
  • Users need the separate Order Material Type to support their own reporting needs. In addition, they want to be able to have values that may be less or more granular than the item material type list would be, since it’s supporting different needs.

Requirements:

  • Allow the user to add, edit and delete values from the list of "Order material types" in the Orders module settings
  • You should not be able to remove a value that is in use by one or more orders
  • Each purchase order line can be assigned 1 order material type
  • Should Not be a required field
  • Should always be editable
  • Should be an alphanumeric value
  • Change label of existing "Material type' field to "Item material type"


 Comments   
Comment by Sharon Beltaine [ 08/Oct/20 ]

Note from Reporting SIG RM Reports working group:
This may have an impact on reports being developed for purchase orders that need to show material type. We cannot pull the material type for the instance from inventory (as suggested in the workaround). We do not see a way to connect the instance to the order. We cannot show the material type associated with the purchase order until the material type field is developed in the Orders app or there is a link from instance to purchase order.

Comment by Dennis Bridges [ 02/Dec/20 ]

I believe these requirements could also be address by adding the Custom Fields functionality to orders. This was recently implemented in the users app and could be repurposed for orders. I believe it may address other similar requirements at the same time and negate the need for adding more individual controlled vocabularies to this record. Allowing some libraries to scale up and some libraries to maintain a simple list of data points. see https://folio-org.atlassian.net/wiki/pages/viewpage.action?spaceKey=FOLIJET&title=MODCFIELDS-39+-+Custom+Field+backend+demo for more detail on this proposed solution.

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