[open-ils-commits] r17682 - trunk/Open-ILS/src/edi_translator (atz)

[svn at svn.open-ils.org]

Author: atz
Date: 2010-09-15 01:25:00 -0400 (Wed, 15 Sep 2010)
New Revision: 17682

Modified:
   trunk/Open-ILS/src/edi_translator/README
Log:
Update README

Modified: trunk/Open-ILS/src/edi_translator/README
===================================================================
--- trunk/Open-ILS/src/edi_translator/README	2010-09-15 05:24:59 UTC (rev 17681)
+++ trunk/Open-ILS/src/edi_translator/README	2010-09-15 05:25:00 UTC (rev 17682)
@@ -26,7 +26,7 @@
 There is no such thing (yet?) as "push" from a vendor of their EDI responses.  Basically
 they just put responses in an FTP directory somewhere that you are expected to check.  It
 would be cool if there were a better way to do that like consuming some RSS feed or 
-remote API callbacks.  
+remote API callbacks.  Similarly, nobody seems willing to utilize interactive EDI.  
 
 Evergreen will only support one delivery address per PO.  That limitation is based
 on the mapping to the delivery address via the ordering_agency org_unit.  If items
@@ -36,10 +36,5 @@
 on SAN, add a new one on SAN + profile_code.  Profile code then goes in the template.
 The template logic could get rather complex to support all the optional data elements.
 
-mbklein says:
-'order' mapper won't work for EDIFACT versions later than D.96A, because of a change
-to the structure of the BGM segment.  But as long as all the supported vendors will
-accept a D.96A ORDERS (which I think they do), that's not a problem.
-
 SEE ALSO:
     http://github.com/mbklein/openils-mapper