Wishlist: Add ability to require fields per provider

Bug #2065784 reported by Tiffany Little
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Evergreen
New
Wishlist
Unassigned

Bug Description

Wishlist.

We have several fields in line items that can block activation -- branch, fund or price. However, if you're submitting an EDI order to a vendor who does cataloging/processing, there may be fields they need to receive to properly process items and those aren't currently required.

For example, I met with Ingram a few weeks ago about utilizing collection codes. They said that collection codes offer granularity for how libraries want their items processed, but if there's one collection code missing in an order it hangs up the entire order.

So my idea would be that per-provider there would be a way to specify additional required fields. Kind of like how we can specify holdings subfields. Then PO activation would also check if there are any blocking fields when doing the activation check, and if any line items are missing that data. If libraries aren't getting cataloging/processing or using EDI, they never need to fill out that info. But if they are and it's necessary, it's another check that they're sending complete info to the vendor.

The things I can think that might be useful that might need to be sent to the vendor are collection code and shelving location, although I'm sure there are more.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.