ORDER record copy-level data for "enriched" EDI

[Bill Erickson]

Some ACQ vendors support delivery of copy-level data via EDI in ORDER messages.

One example work-flow:

1. create order on vendor site
2. download/ftp order record from vendor and push into ILS
3. activate order to generate enriched EDI and deliver to vendor, which activates the order on the vendor side w/ copy data
4. vendor later provides better MARC records (potentially w/ shelf-ready copy data) which are mapped back into Evergreen. (LP pending for auto-mapping via Vandelay).

Code in progress lives at:

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/berick/acq-edi-orders-with-copies

The basic functionality is there, but it needs more real-world testing. Will add 'pullrequest' tag after more testing and squashing.

------

This functionality requires some changes to the Ruby openils-mapper libs. Those changes live here for now (2 commits):

http://git.evergreen-ils.org/?p=working/random.git;a=shortlog;h=refs/heads/collab/berick/openils-mapper

Original code comes from https://github.com/mbklein/openils-mapper

After some more testing and cleanup, I'll set up a pull-request on Github for mainline integration.

[Bill Erickson (berick)]

For reference, link to the pending LP ticket for Vandelay copy overlay : bug #1031144

[Bill Erickson (berick)]

Pushed some repairs and did some squashing to working => collab/berick/acq-edi-orders-with-copies-squash

* Note the branch contains a signed-off commit I got from Lebbeous for an EDI test script

From the main commit (to refresh):

Adds a new "copies" structure to the stock JEDI ORDER template. Copies are ultimately mapped into one or more GIR segments in the outbound EDI. This commit only adds the change to the stock template (seed data). It also adds entries to the environment for the stock template and existing template 23 via upgrade script (to expedite local template editing).

With the current template, GIR segments look like so:

GIR+001+8:LCO+TESTFUND2:LFN+SYS1-BR1:LLO+FIC ROW 456:LSM+Stacks:LSQ'
GIR+002+9:LCO+TESTFUND2:LFN+SYS1-BR1:LLO+FIC ROW 456:LSM+Stacks:LSQ'
GIR+003+10:LCO+TESTFUND2:LFN+SYS1-BR1:LLO+FIC ROW 456:LSM+Stacks:LSQ'
GIR+004+11:LCO+TESTFUND2:LFN+SYS1-BR1:LLO+FIC ROW 456:LSM+Stacks:LSQ'
GIR+005+12:LCO+TESTFUND2:LFN+SYS1-BR1:LLO+FIC ROW 456:LSM+Stacks:LSQ'
GIR+006+13:LCO+TESTFUND2:LFN+SYS1-BR2:LLO+FIC ROW 456:LSM+Young Adult:LSQ'
GIR+007+14:LCO+TESTFUND2:LFN+SYS1-BR2:LLO+FIC ROW 456:LSM+Young Adult:LSQ'
GIR+008+15:LCO+TESTFUND2:LFN+SYS1-BR2:LLO+FIC ROW 456:LSM+Young Adult:LSQ'

LQT / quantity is also supported.

The current implementation is meant to cover all possible fields so that users can remove/alter items on a vendor by vendor basis as needed.

[Mike Rylander (mrylander)]

ENRICHED EDI! YEAH! THANKS! Merged to master for 2.3 goodness.

[Bill Erickson (berick)]

For reference, the openils-mapper code now lives on github as a fork of the original code, plus topic branch:

https://github.com/berick/openils-mapper/tree/GIR-segments-for-copy-data

Pullrequest pending

[Mary Llewellyn (mllewell)]

Is there a way that copy ID# could be coded into the enriched EDI? We've been using that as a match point for Baker & Taylor cataloged items when we load them to replace the acq item values.

[Bill Erickson (berick)]

Mary, it is possible to include the copy ID. (It's the "LCO" value in the sample above). It a matter of changing the template to include the "copy_id" field with each copy. As an example, I'm working on an improved general-purpose EDI order template here:

http://git.evergreen-ils.org/?p=evergreen/equinox.git;a=blob;f=edi_order.tt2;h=5135f4d03b07950746c71ce31d5dd7259ff1b67d;hb=refs/heads/acq-order-edi-template

Search down for "copy_id", near the bottom.

I'll be posting this template to a new LP ticket soon.

Note that it's the ACQ copy ID and not the catalog copy ID, however changes to Vandelay (if the goal is to use Vandelay copy overlays) allow it to match on ACQ copy ID or catalog copy ID, depending the selected queue type (acq vs. bib).

[Bill Erickson (berick)]

... and by template change, I'm referring to the "PO JEDI" action/trigger event definition template.