Move EDI toggles into DB

[Bill Erickson]

This should be a precursor to bug #1373690.

The goal is to move all of the per-vendor switches from the EDI template and link them to the edi_account in the database. This will clean up the template and make it possible to toggle settings without having to edit the template. It will also allow us to do more pre-template data munging when generating EDI, so that the template itself retains little or no logic, minus a few loops.

Examples of settings/flags I'd like to see moved are whether or not to include copies, whether to include, say, the call number, whether to include the PO name in the PO identifier, etc. I've identified about 15 toggles so far that could be taken out of the template.

While we're in here, we could also add flags for whether an edi_account sends order, receives responses, and/or receives invoices.

I imagine we could do this a couple of ways. My current thinking is to create a table (acq.edi_attribute) which is simply a list of attribute types and a mapping table (acq.edi_account_attr_map) which links attributes to an account. Each attribute acts as a boolean toggle, so when an attribute ("include copies") is linked, then it's "true" for that account.

Tangentially related to this is the desire to support org unit (etc.) mapping tables to provide shortened values for certain fields (e.g. org unit shortname) for vendors that have field length limitations in EDI. The plan so far does not include support for this, but I could imagine extending the design to add it. Comments welcome.

[Bill Erickson (berick)]

Work on this progresses in bug #1373690.

[Bill Erickson (berick)]

This and bug #1373690 are now a single project. Marking this as duplicate.