Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-1381

CRUD for EDIFACT Invoice Field Mapping Profiles

    XMLWordPrintable

    Details

    • Template:
    • Analysis Estimate:
      Large < 10 days
    • Front End Estimate:
      Large < 10 days
    • Back End Estimate:
      XL < 15 days
    • Confidence factor:
      Low
    • Estimation Notes and Assumptions:
      Estimate by Ann-Marie and Folijet
    • Development Team:
      Folijet
    • Calculated Total Rank:
      107
    • PO Rank:
      105
    • Rank: Chalmers (Impl Aut 2019):
      R4
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: FLO (MVP Sum 2020):
      R4
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: hbz (TBD):
      R2
    • Rank: Hungary (MVP End 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: Leipzig (Full TBD):
      R2
    • Rank: Leipzig (ERM Aut 2019):
      R2
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R1

      Description

      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:

      1. What additional documentation is needed?
      2. How much of the field identification may be handled by the EDIFACT parser, e.g. Smooks
      3. See Hein sample invoice - why < instead of +?

      Note: Split from UXPROD-656 because it was too broad, and so that it could be closed in Q4 2018

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                abreaux Ann-Marie Breaux
                Reporter:
                abreaux Ann-Marie Breaux
                Analysis Estimator:
                Ann-Marie Breaux Ann-Marie Breaux
                Front End Estimator:
                Ann-Marie Breaux Ann-Marie Breaux
                Back End Estimator:
                Oleksii Kuzminov Oleksii Kuzminov
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases