SPIKE: Gather details on mapping MARC to Orders

Description

  • Gather necessary details for mapping MARC to Orders

  • Define whether Processor needs to be changed (probably not since we won't have default mapping rules)

  • Create wiki page

  • Create implementation stories for di-core

See details https://folio-org.atlassian.net/wiki/display/DD/Import+Orders+in+MARC+format

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

UIDATIMP-294

And PPT: https://docs.google.com/presentation/d/1BJz5_71L9pCxIBvYO2yygcVdV_0amTrcnakGYB9aeeY/edit#slide=id.p1

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:

Ann-Marie Breaux September 20, 2022 at 7:40 AM

Hi Please also see the developer questions section of https://folio-org.atlassian.net/wiki/display/MM/Create+orders+by+importing+MARC+Bibliographic+Records, and feel free to add anything for Thunderjet there, especially down in the "Data elements" area.

In the meantime:

  1. "approvedById": I added a question for Tjet on the wiki page

  2. "approvalDate": I added a question for Tjet on the wiki page

  3. "assignedTo": On Order field mapping profile - 3 slide, end of row 2 - this will be a User name or ID; this is optional

  4. "closeReason": Not needed; orders can only be created by DI as Pending or Open, not Closed

  5. "dateOrdered": I added a question for Tjet on the wiki page

  6. "ongoing" (there are some fields inside, such as: "interval","isSubscription","manualRenewal","notes","reviewPeriod","renewalDate","reviewDate"). We decided to skip this one, correct if I'm wrong. Correct - DI will only create One-time orders, not Ongoing orders, so none of these fields are needed

  7. "template" - we decided to skip this one, correct if I'm wrong. Correct. The MARC records and the field mapping profile replace the order template for orders created via DI

  8. "tags" - we decided to skip this one, correct if I'm wrong. Correct. DI cannot currently import tag data

Volodymyr Rohach September 19, 2022 at 3:01 PM

Hi ! 

Regading missmatching list of fields, which I can't find in the mapping profile from presentation (Field mappings for orders - Google Презентации)  and back-end entity "

CompositePurchaseOrder":

  1. "approvedById"

  2. "approvalDate"

  3. "assignedTo"

  4. "closeReason"

  5. "dateOrdered"

  6. "ongoing" (there are some fields inside, such as: "interval","isSubscription","manualRenewal","notes","reviewPeriod","renewalDate","reviewDate"). We decided to skip this one, correct if I'm wrong.

  7. "template" - we decided to skip this one, correct if I'm wrong.

  8. "tags" - we decided to skip this one, correct if I'm wrong.

 

Basically, that's all for now.   Could you please review these fields and decide what should we do with them? Just skip, or extend our design for mapping profile. Thank you!

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Folijet

Release

Orchid (R1 2023)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created August 26, 2022 at 1:34 PM
Updated February 2, 2023 at 6:49 AM
Resolved September 29, 2022 at 2:23 PM
TestRail: Cases
TestRail: Runs