Confirm that a MARC mapping and/or default will work for POL Account field
Description
CSP Request Details
CSP Rejection Details
Potential Workaround
Attachments
blocks
defines
relates to
Checklist
hideTestRail: Results
Activity

Maksym Ishchenko February 10, 2023 at 4:23 PM
Hi
Tested on snapshot env. All mappings for account numbers works good. Closing this issue.
Screencast:
cc:

Ann-Marie Breaux February 8, 2023 at 7:03 AM
Hi I tested in Snapshot, and looks like the mapping is working fine. Thank you!
Hi Please see TestRail https://foliotest.testrail.io/index.php?/cases/view/376604. I created it using 1 field mapping profile, and the MARC file that is attached to the test. Imported the file once to check one version of field mapping for the account number field. Then edited the field mapping profile and imported the file again to check a second version of field mapping for the account number. Then edited the field mapping profile again and imported the file again to check a third version of field mapping for the account number.
Profiles are set up in Snapshot right now, so that you could start with step 8 of the test, if you want to run through the steps. And let me know if this seems OK as a way to test different mapping variations for 1 field in the field mapping profile. If so, I'll use the same format for tests of other fields (like fund, expense class, etc.) Thank you!

Ruslan Lavrov February 7, 2023 at 8:27 AM
Hi , we are waiting for testing from our QA engineers.

Ann-Marie Breaux February 7, 2023 at 7:42 AM
Hi and Yes, we can close it. Do you mean the additional testing has already been done, or still needs to be done?

Kateryna Senchenko February 6, 2023 at 2:44 PM
, this case was covered in the implementation MODORDERS-773, can we close this issue as a Not a bug after additional testing?
Details
Details
Assignee

Reporter

Purpose: To confirm that a value in a MARC field/subfield can be mapped into the Account field of a POL without errors
As a staff person working with MARC Bib order data
I want FOLIO to be able to handle Account MARC data cleanly
So that I can use it to populate the POL's Account field
Note that FOLIO does not validate the Account field's values and does not require the POL's Account field value to be an Account documented in the PO's Organization record.
Scenarios
Scenario 1
Given the Data Import field mapping profile
When a user specifies a MARC field and subfield for the POL Account
Then use that data to populate the POL Account field
Testing
Test using 3 different field mapping profiles with 3 different mappings.
Mapping 1
Vendor field mapping: Look up GOBI in Organizations and use as default
Account field mapping: 982$a
Incoming data: 982 $a12345-1 (is not an account in the GOBI Organization record, but should be able to populate the POL Account field without an error)
Mapping 2
Vendor field mapping: Look up GOBI in Organizations and use as default
Account field mapping: 982$a; else "99999-10"
Incoming data: no 982 (no 982, so will use the else logic and assign 99999-10 in the POL Account field
Mapping 3
Vendor field mapping: Look up GOBI in Organizations and use as default
Account field mapping: "99999-10"
Incoming data: 982 $a12345-1 (no MARC mapping in the field mapping, so import will ignore 982$a and use the default mapping of 99999-10 to populate the POL Account field)