CRUD for EDIFACT Invoice Field Mapping Profiles
Description
Priority
Fix versions
Development Team
Folijet
Assignee

Solution Architect
None
NoneParent Field Value
None
Parent Status
None
defines
is continued by
is defined by
relates to
Checklist
hideTestRail: Results
Activity
Show:
Done
Details
Details
Reporter

PO Rank
105
Estimation Notes and Assumptions
Estimate by Ann-Marie and Folijet
Analysis Estimate
Large < 10 days
Analysis Estimator

Front End Estimate
Large < 10 days
Front End Estimator

Front-End Confidence factor
Low
Back End Estimate
XL < 15 days
Back End Estimator

Rank: FLO (MVP Sum 2020)
R4
Rank: 5Colleges (Full Jul 2021)
R1
Rank: Cornell (Full Sum 2021)
R1
Rank: Chalmers (Impl Aut 2019)
R4
Rank: GBV (MVP Sum 2020)
R2
Rank: hbz (TBD)
R2
Rank: Hungary (MVP End 2020)
R1
Rank: TAMU (MVP Jan 2021)
R1
Rank: Chicago (MVP Sum 2020)
R1
Rank: Leipzig (ERM Aut 2019)
R2
Rank: MO State (MVP June 2020)
R1
Rank: U of AL (MVP Oct 2020)
R1
Rank: Leipzig (Full TBD)
R2
Rank: Lehigh (MVP Summer 2020)
R1
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created December 3, 2018 at 8:57 AM
Updated June 8, 2021 at 6:11 AM
Resolved April 28, 2021 at 2:49 AM
TestRail: Cases
TestRail: Runs
Help the user set mapping rules and profiles for dealing with incoming batch loads:
Create field mapping screen for invoice and invoice lines
Identify data elements in fields of incoming EDIFACT invoice file
Define mapping syntax for EDIFACT data elements mapping to FOLIO Invoice records
Include default field mapping profiles for vendors identified by libraries, which can be edited, duplicated, and deleted by libraries
Same field mapping detail options as in Inventory field mappings
Allow for sequential mapping (first look in this field for data, then in this field)
Allow for defaults
Allow for mappings to be created and saved as data mapping profiles
Apply the rules to parse the incoming data and deliver to the appropriate FOLIO loader apps, to CRUD the proper kinds of records
See Google folder: https://drive.google.com/drive/folders/1ePm2M3FcHIZFVolxD4-WX8joEc1S_iVC
with
Sample invoices from various vendors
EDItEUR documentation for monographic and subscription invoices
Default invoice field mapping profiles to be supplied with FOLIO
A syntax document (will probably need updates)
Questions:
What additional documentation is needed?
How much of the field identification may be handled by the EDIFACT parser, e.g. Smooks
See Hein sample invoice - why < instead of +?
Note: Split from because it was too broad, and so that it could be closed in Q4 2018