Comment 4 for bug 1373690

I've decided to take this a step further. In combination with bug #1513872 (moving EDI toggles into the database), I'm working on a branch to generate EDI directly within the Perl code, no Ruby or Action/Trigger required.

The code is far enough along at this point to generate what appears to be sane and correct EDI. It is not yet integrated into the EDI delivery process.

To test:

1. Install the new code and SQL changes
2. cd Open-ILS/src/support-scripts/test-scripts
3. ./edi_writer.pl --po-id <test-PO-ID-of-choice>
4. The script prints EDI to STDOUT.

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/berick/lp1513872-acq-edi-account-attrs-wip

==

By moving everything in the Perl code, we lose the flexibility we had using A/T templates. The goal is to represent all vendor-specific tweaks as edi_attr's (from the new SQL) so that local template tweaks are not required. (For my part, editing Perl instead of TT templates and removing the A/T steps make building and testing this code significantly faster and easier).

Question for the room... How did you modify your EDI (event_def 23) templates from the stock version?