Import Orders in MARC format

Description

Combined with UXPROD-2282, which was closed as a duplicate

Split the Acq record types (orders and invoices) from the Inventory and MARC record types (UXPROD-2075, UXPROD-2286)

See the Syntax and Field Types tabs of https://drive.google.com/open?id=17kCccovBR-RAVK-coW7fpXvJfaRmYA2mUHoVLSF9Spo for field mapping syntax details

Main work in this feature will be the Order field mapping profile

Help the user set mapping rules and profiles for dealing with incoming batch loads:

  • Find data elements in fields of incoming MARC Bibliographic file

  • Map to data elements of appropriate FOLIO Acquisitions records

  • Same field mapping options as MARC Inventory field mapping profiles

    • Allow for sequential mapping (first look in this field for data, then in this field)

    • Allow for defaults

    • Allow for blanking out data in existing FOLIO fields A-M check is this is needed - maybe only create, not update?

    • Allow for mappings to be created and saved as data mapping profiles, or to be created on the fly

    • Apply the rules to parse the incoming data and deliver to the FOLIO Orders app, to create orders and order lines

--------------

Bring job profiles to life for MARC Bibliographic records creating (not yet deleting) Order + Order line records

Note: This is based on UI input, not command line. Data Migration may take care of loading PO and PO Line data based on command line interaction with Order APIs.

Parse incoming order data in MARC records to identify relevant order details, package them up, and deliver to the orders app with appropriate rules, so that orders and order lines can be created.

When start importing orders and shelfready data, preference is to match on PO or Order Key and then update associated Instance, MARC Bib, Holdings, Items – make sure this is a requirement in the order import (see UXPROD-3345)

See additional details here: https://folio-org.atlassian.net/wiki/display/MM/Create+orders+by+importing+MARC+Bibliographic+Records

Priority

Fix versions

Development Team

Folijet

Assignee

Solution Architect

Parent Field Value

None

Parent Status

None

defines

is continued by

is defined by

Checklist

hide

TestRail: Results

Activity

Show:

Ann-Marie BreauxJune 7, 2023 at 3:32 AM

Hi I'm curious why this completed Folijet feature was reassigned to Spitfire. Was it perhaps a mistake? OK if I switch it back?

Julie Brannon (old account)February 28, 2023 at 7:12 PM

Is this feature still included in Orchid?  I'm looking at Test Rail for the upcoming BugFest and I'm not seeing test cases related to MARC import to create orders, so I wondered if maybe it will be included in Poppy instead?  Or I also might be completely missing them in Bug Fest .  Thanks!

Ann-Marie BreauxFebruary 7, 2023 at 8:18 AM
Edited

Hi This feature (https://folio-org.atlassian.net/browse/UXPROD-185#icft=UXPROD-185) will be completed in Orchid. I don't know when https://folio-org.atlassian.net/browse/UXPROD-663#icft=UXPROD-663 will be completed. I left a comment on that feature a few minutes ago, based on a question from Erin. https://folio-org.atlassian.net/browse/UXPROD-3814#icft=UXPROD-3814 will probably be in the Quesnelia release, once libraries have a chance to work with the functionality of https://folio-org.atlassian.net/browse/UXPROD-185#icft=UXPROD-185. And of course if there are signficant bugs for https://folio-org.atlassian.net/browse/UXPROD-185#icft=UXPROD-185, we'll aim to take care of them during Orchid Bugfest or Poppy.

Charlotte WhittFebruary 6, 2023 at 5:30 PM
Edited

Hi - in a meeting we are trying to understand the connection between:

Which feature is to be done first, and which to be done after the other.

CC:

Ann-Marie BreauxOctober 7, 2022 at 1:59 PM

Development has not proceeded as quickly as I hoped on this (complexity of sorting out the requirements across 2 dev teams, shortened Nolana dev period, varying functionality in Orders and Import apps). Spoke with Data Import Subgroup and Acquisitions SIG this week to explain that we will be delaying the release until Orchid, so that we have time to put all of the pieces together, identify gaps in the basic workflow, and have solid UAT. Updated the feature and all linked stories from Nolana to Orchid release value

Done

Details

Reporter

PO Rank

135

Analysis Estimate

Large < 10 days

Analysis Estimator

Front End Estimate

XL < 15 days

Front End Estimator

Front-End Confidence factor

90%

Back End Estimate

XXL < 30 days

Back End Estimator

Back-End Confidence factor

90%

Release

Orchid (R1 2023)

Rank: FLO (MVP Sum 2020)

R1

Rank: 5Colleges (Full Jul 2021)

R1

Rank: Cornell (Full Sum 2021)

R1

Rank: Chalmers (Impl Aut 2019)

R5

Rank: GBV (MVP Sum 2020)

R5

Rank: hbz (TBD)

R1

Rank: Hungary (MVP End 2020)

R1

Rank: Grand Valley (Full Sum 2021)

R2

Rank: MI State-Lib of MI (Sum 2021)

R1

Rank: TAMU (MVP Jan 2021)

R1

Rank: Chicago (MVP Sum 2020)

R1

Rank: Leipzig (ERM Aut 2019)

R5

Rank: MO State (MVP June 2020)

R1

Rank: U of AL (MVP Oct 2020)

R4

Rank: Leipzig (Full TBD)

R5

Rank: Spokane Public Library (Jan 2021)

R2

Rank: Lehigh (MVP Summer 2020)

R1

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created January 20, 2018 at 12:42 PM
Updated October 30, 2024 at 6:11 PM
Resolved April 5, 2023 at 6:19 AM
TestRail: Cases
TestRail: Runs