Thank you for compiling this feedback!
Item Details - Purchase Material ID - This is intended to denote the Product/material ID for the physical or electronic item. It has been split into two potential fields in the latest mockup.
Manual Batching: That is correct, the system will batch lines based on Vendor and Date unless Manual Batching has been checked. If it has, only the lines you have in your current Purchase Order will be grouped together.
Donor: We have yet to determine how it will be passed to the public interface, hower as we collected it her we can expose it or forward it as needed
Collection: This is a flag to indicate whether the order is for a collection of items or not. The small group believed this would be valuable to indicate and would encourage further discussion as to possible uses.
Aquisition Methods: The current list includes - Approval Plan, Depository, Exchange, Gift, Legal Deposit, Technical, Purchase at Vendor System - The goal is to allow administrators to manage this list in their instance.
These functionality suggestions are excellent, we intend to leverage “default settings” as much as possible to speed the creation of new orders. Claim details are on that list, unfortunately, we don’t have an intuitive way to represent these details in the current mockup. We will work on clarifying these in our next update to documentation.
We are still narrowing down what fields will be editable, but are leaning towards opening as many as possible for version one as integrations/data source options will be limited.
Deleting PO and POL: PO and POL each have statuses. When in certain statuses they cannot be deleted (Eg. PO = Sent) but they could be canceled. The model essentially allows for available actions for PO or POL to be dependant on status.
The feedback regarding e-resource details for items that don’t require payment is something we need to discuss further. However, in certain scenarios, these details seem to be required here. Thus, we will likely need to keep them for the time being and discuss how we may address this with functionality in receiving or elsewhere?