Overview : When creating orders with an order format of electronic, an instance, and a holdings records from a MARC bibliographic record using Data Import, the quantity in both the ‘Cost details' and ‘Location’ section of the POL is ‘0' despite the field mapping profile instructing it be '1’.

Reproduction :

• This error was reproduced in bugfest-poppy on 2/27/2024.

• In the Data Import app, Job 12520 and Job 12526 both demonstrate the error.

  • Both use Job profile ‘CAH Create Full Cat / Electronic’ (I changed the receipt status between each job, but it had no effect on the quantity issue.)

    • POLs : 44183-1, 44181-1

  • In both jobs, the POL has a quantity = 0 for the cost details and location regardless of the instruction in the field mapping profile (CAH Electronic approvals order) being “1”.

• The file used for this test is attached (51639_test1.mrc).

Additional information :

• Originally noted in a Poppy CSP#1 environment.

• When ‘CAH Create Full Cat / Electronic #2’ is used as the job profile, the quantity = 1 as expected. This profile creates only the order and instance. Subsequent testings shows that it also works if only the order is created. It’s only when the holdings record creation is added that it fails.

• This error has a huge impact as it prevents encumbrances from processing properly.

• Using a nearly identical profile with the ‘Order format’ = ‘Print resource’, this error was not observed.
  
  

Requirements per SME conversations:
Quantity value within Orders should not be tied to the number of Items created as part of a Job. Instead, it is expected that the field mapping profile should always determine the Quantity value.

Critical service patch details

1. Describe issue impact on business - When creating orders with an order format of electronic, an instance, and a holdings records from a MARC bibliographic record using Data Import, the quantity in both the ‘Cost details' and ‘Location’ section of the POL is ‘0' despite the field mapping profile instructing it be '1’.

2. What institutions are affected? (field “Affected Institutions” in Jira to be populated) - All.

3. What is the workaround if exists? No workaround.

4. What areas will be impacted by fix (i.e. what areas need to be retested) - mod-data-import, mod-orders

5. Brief explanation of technical implementation and the level of effort (in workdays) and technical risk (low/medium/high). - Revert Orders/Holdings/Items Location & Quantity ‘Check’ and ‘Overlay’ logic that was introduced in Poppy. Low risk.

6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO.  - Low effort.

7. What is the roll back plan in case the fix does not work? Revert to previous version.