Activity log for bug #1172373

Date Who What changed Old value New value Message
2013-04-24 17:55:21 Lebbeous Fogle-Weekley bug added bug
2013-04-24 17:55:31 Lebbeous Fogle-Weekley nominated for series evergreen/2.3
2013-04-24 17:55:31 Lebbeous Fogle-Weekley bug task added evergreen/2.3
2013-04-24 17:55:31 Lebbeous Fogle-Weekley nominated for series evergreen/2.4
2013-04-24 17:55:31 Lebbeous Fogle-Weekley bug task added evergreen/2.4
2013-04-24 17:55:36 Lebbeous Fogle-Weekley evergreen/2.3: milestone 2.3.7
2013-04-24 17:55:40 Lebbeous Fogle-Weekley evergreen/2.4: milestone 2.4.0-rc
2013-04-24 18:01:57 Lebbeous Fogle-Weekley description Evergreen 2.3+ EDI Invoices from book vendors have a segment where we try to parse out a number that's supposed to point to the purchase order related to a PO. There are problems with this. 1) Invoices usually reference lineitems that came from many different POs, and there's only ever at most one PO # in this field in practice. (And I'm not addressing this problem for now, just noting it for the record). 2) Some vendors put alphanumeric strings in here instead of the PO id. And I mean values that aren't the PO's name field, either. In some cases, the string is just the vendor's name! It's problem 2 I'm addressing for now. Since the existing code wants to match these numbers to a PO in the system, I'm still leaving that in place as long as the string given by the vendor is all digits. If the string is not all digits, then we just proceed without looking for a PO or setting any value in the purchase_order column of the acq.edi_message row we're creating. http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/senator/acq-edi-po-field-unreliable Evergreen 2.3+ EDI Invoices from book vendors have a segment where we try to parse out a number that's supposed to point to the purchase order related to the invoice. There are problems with this. 1) Invoices usually reference lineitems that came from many different POs, and there's only ever at most one PO # in this field in practice. (And I'm not addressing this problem for now, just noting it for the record). 2) Some vendors put alphanumeric strings in here instead of the PO id. And I mean values that aren't the PO's name field, either. In some cases, the string is just the vendor's name! It's problem 2 I'm addressing for now. Since the existing code wants to match these numbers to a PO in the system, I'm still leaving that in place as long as the string given by the vendor is all digits. If the string is not all digits, then we just proceed without looking for a PO or setting any value in the purchase_order column of the acq.edi_message row we're creating. http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/senator/acq-edi-po-field-unreliable
2013-04-25 18:17:35 Ben Shum evergreen: status New Triaged
2013-04-25 18:17:36 Ben Shum evergreen/2.3: status New Triaged
2013-04-25 18:17:38 Ben Shum evergreen/2.4: status New Triaged
2013-04-25 18:17:40 Ben Shum evergreen: importance Undecided Medium
2013-04-25 18:17:42 Ben Shum evergreen/2.4: importance Undecided Medium
2013-04-25 18:17:44 Ben Shum evergreen/2.3: importance Undecided Medium
2013-04-27 05:29:34 Ben Shum evergreen/2.4: milestone 2.4.0-rc
2013-05-19 20:11:31 Ben Shum evergreen/2.3: milestone 2.3.7
2013-06-05 14:26:56 Mary Llewellyn bug added subscriber Mary Llewellyn
2013-06-07 19:41:32 Ben Shum evergreen: status Triaged Incomplete
2013-06-12 21:09:01 Dan Wells evergreen: milestone 2.5.0-m1 2.5.0-m2
2013-06-21 21:28:30 Lebbeous Fogle-Weekley evergreen: assignee Lebbeous Fogle-Weekley (lebbeous)
2013-06-24 19:37:21 Christine Morgan bug added subscriber Christine Morgan
2013-07-15 16:15:01 Dan Wells evergreen: milestone 2.5.0-m2 2.5.0-alpha1
2013-08-05 18:20:02 Mary Llewellyn attachment added acq, EDI invoicing https://bugs.launchpad.net/evergreen/+bug/1172373/+attachment/3761726/+files/Bridgeport%20EDI%20invoice%20example.docx
2013-08-07 03:01:10 Ben Shum evergreen/2.3: milestone 2.3.10
2013-08-07 03:01:12 Ben Shum evergreen/2.4: milestone 2.4.2
2013-08-07 03:01:15 Ben Shum evergreen: assignee Lebbeous Fogle-Weekley (lebbeous)
2013-08-07 03:01:18 Ben Shum evergreen: status Incomplete Fix Committed
2013-08-07 03:01:20 Ben Shum evergreen/2.3: status Triaged Fix Committed
2013-08-07 03:01:21 Ben Shum evergreen/2.4: status Triaged Fix Committed
2013-11-11 17:37:58 Ben Shum evergreen: status Fix Committed Fix Released
2013-11-11 17:38:01 Ben Shum evergreen/2.4: status Fix Committed Fix Released
2013-11-11 17:38:03 Ben Shum evergreen/2.3: status Fix Committed Fix Released