Details
-
Bug
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
Prokopovych - Sprint 156, Prokopovych - Sprint 157, Prokopovych - Sprint 158
-
Prokopovych
-
Orchid (R1 2023)
Description
Overview: I'm getting 404 error for GET request 'https://folio-testing-cypress-okapi.ci.folio.org/inventory/instances/undefined'
**
Preconditions:
- The user is logged into application.
- Open the MARC file and note the bibliographic information for the first record.
Steps to Reproduce: **
- Go to the Orders app and create a new PO by clicking Actions/New on the Orders.
- Fill in the following PO details
-
- Organization lookup: find an active vendor and assign, (e.g. GOBI Library Solutions)
- Order type: One-time
Save and close
3. Scroll down to the PO Line section of the PO and click Actions/Add PO line
4. Fill in the following POL details:
-
- Title (copy from the MARC record you'll be importing later)
- Product ID (e.g. ISBN), Product ID Type
- Acquisition method: select Purchase at vendor system
- Order format: select Physical resource
- Click "Add vendor reference number" and add a number or alpha-numeric in the field, then select "Vendor order reference number" from the Reference type dropdown list
- NOTE: Make sure that vendor reference number is not being used as VRN for any other orders in that FOLIO tenant
- Physical unit price: 20
- Physical unit quantity: 1
- Fund distribution: skip this accordion
- Location: select a location from the drop-down list
- Quantity physical: 1
- Create Inventory: Make sure it is set to create Instance, holdings, item
- Material type: select one from the drop-down list
Save and close
5. Note the VRN, so that you can add it to the MARC record
6. Go to the purchase order and click Actions/Open, then confirm that you want to open the order.
7. Open your MARC file of 2 cataloging records and make the following updates to the first record
-
- Create an 024 field, 1st indicator = 8, 2nd indicator = [blank], $a FOLIO VRN(example: 024 8 $a3123621786817
- If there are pre-existing 024s in the MARC record, make sure this newly-created 024 is the FIRST 024 in the record.
- Create a 980 field, blank indicators, $a location code (e.g. KU/CC/DI/M - make sure it's a valid location code for the tenant you'll be importing to) $b copy the first part of the LC call number from the 050 $a data, or else make one up if there is no 050 $c copy the second part of the LC call number from the 050 $b data, or else make one up if there is no 050
- Create a 981 field, blank indicators, $a 1, $bnumeric, e.g. 3782137819 (will be the item barcode number - must be unique in the particular FOLIO tenant)
8. Create similar 980/981 fields in the second record, but DO NOT create an 024 field.
Save your .mrk file and recompile into a .mrc file.
This will be the import file.
The first record should match to the Instance, Holdings, and Item, and update according to the action and field mapping profiles.
The second record will not match, so it will not update anything in Inventory.
9. Go to Settings/Data Import and create the following profiles. You may want to use the Test or Case number as the beginning of the profiles' names, to make them easier to find and connect with each other.
-
- 3 field mapping profiles
- 3 action profiles
- 3 match profiles
- 1 job profile
10. Field mapping profile 1
-
- Name: Update Instance by VRN match
- Incoming record type: MARC Bibliographic
- FOLIO record type: Instance
- Cataloged date: ###TODAY###
- Instance status term: select one from the dropdown list
Save and close
11. Field mapping profile 2
-
- Name: Update Holdings by VRN match
- Incoming record type: MARC Bibliographic
- FOLIO record type: Holdings
- Holdings type: Monograph
- Permanent location: 980$a
- Call number type: select Library of Congress from the dropdown list
- Call number: 980$b " " 980$c
Save and close
12. Field mapping profile 3
-
- Name: Update Item by VRN match
- Incoming record type: MARC Bibliographic
- FOLIO record type: Item
- Barcode: 981$b
- Copy number: 981$a
- Status: Select Available from the dropdown list
Save and close
13. Create 3 action profiles and link to the 3 field mapping profiles you just created. Action profiles will be:
-
- Update Instance
- Update Holdings
- Update Item
14. Match profile 1:
-
- Name: 024 $a VRN to Instance VRN
- Incoming records: MARC Bibliographic
- Existing records: Instance
- Incoming MARC Bib:
- Field: 024
- Ind 1: 8
- Ind 2: *
- Subfield: a
-
- No Qualifier or Only compare part
- Match criterion: Exactly matches
- Existing instance record field: search for VRN, and select that option (will be in the Admin data section of the dropdown list)
Save and close
15. Match profile 2:
-
- Name: 024 $a VRN to Holdings VRN
- Incoming records: MARC Bibliographic
- Existing records: Holdings
- Incoming MARC Bib:
- Field: 024
- Ind 1: 8
- Ind 2: *
- Subfield: a
-
- No Qualifier or Only compare part
- Match criterion: Exactly matches
- Existing holdings record field: search for VRN and select that option (will be in the Admin data section of the dropdown list)
Save and close
16. Match profile 3:
-
- Name: 024 $a VRN to Item VRN
- Incoming records: MARC Bibliographic
- Existing records: Item
- Incoming MARC Bib:
- Field: 024
- Ind 1: 8
- Ind 2: *
- Subfield: a
-
- No Qualifier or Only compare part
- Match criterion: Exactly matches
- Existing item record field: search for VRN and select that option (will be in the Admin data section of the dropdown list
Save and close
17. Job profile:
-
- Name: Update Instance, Holdings, Item based on VRN match
- Accepted data type: MARC
- Overview:
- Instance match
- If match: Update instance
- If no match: Stop
- Holdings match
- If match: Update holdings
- If no match: Stop
- Item match
- If match: Update item
- If no match: Stop
Save and close
18. Go to Data Import and Upload the edited MARC file.
19. Import the updated MARC file, using the newly-created job profile.
20. After the import is completed, click on the file name at the top of the log list.
21. Open DevTools (press F12 button on the Keyboard) and click on the instance Updated hotlink.
22. Open holdings view page.
23. Close holdings view page.
24. Open item view page.
25. Close item view page.
26. Pay attention to requests with error 404 in the request.
Expected Results: The requests with errors are not displayed in the Network tab in DevTools.
Actual Results: The bad requests are triggered in Inventory app after opening item view page.
Additional Information:
URL:
Interested parties:
TestRail: Results
Attachments
Issue Links
- clones
-
UIIN-2272 The bad requests are triggered in Inventory app after opening holdings view page
-
- Closed
-
- defines
-
UXPROD-3815 R1 2023 | Prokopovych Enhancements/Bugfixes/NFR/tech debt
-
- Closed
-