Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
Folijet Sprint 152
-
5
-
Folijet
-
Nolana (R3 2022) Bug Fix
-
!!!ALL!!!
-
Implementation coding issue
Description
Overview:
Preconditions:
- The user is logged into application.
Steps to Reproduce:
- In Settings/Data import, create a new "Field mapping profile" with:
-
- A unique valid name
- Incoming record type: MARC Bibliographic
- FOLIO record type: MARC Bibliographic
- Field mappings for MARC: Modifications
- Modifications:
- Action: Add
- Field: 650
- Ind 1: [blank]
- Ind 2: 4
- Subfield: a
- Subaction: [none]
- Data: Test update
-
- Save the profile
2. Create a new "Field Mapping Profile" with:
-
- A unique valid name
- Incoming record type: MARC Bibliographic
- FOLIO record type: instance
3. Create a new "Field Mapping Profile" with:
-
- Unique valid name
- Incoming record type: MARC Bibliographic
- FOLIO record type: holding
- Permanent location: select any of values from the dropdown list
4. Create a new "Field Mapping Profile" with:
-
- Unique valid name
- Incoming record type: MARC Bibliographic
- FOLIO record type: item
- Material type: select any of values from the dropdown list
- Status: select any of values from the dropdown list
- Permanent loan type: select any of values from the dropdown list
5. Create a new "Action Profile" with:
-
- A unique valid name
- Action: Modify
- FOLIO record type: MARC Bib
Link a profile with mapping profile from step#1
6. Create a new "Action Profile" with:
-
- A unique valid name
- Action: create
- FOLIO record type: instance.
Link a profile with mapping profile from step#2
7. Create a new "Action Profile" with:
-
- A unique valid name
- Action: create
- FOLIO record type: holding.
Link a profile with mapping profile from step#3
8. Create a new "Action Profile" with:
-
- A unique valid name
- Action: create
- FOLIO record type: item.
Link a profile with match profile from step#4
9. Create a new "Job profile" with a unique valid name in it and accepted data type = MARC
All other fields should be filled according to pre-conditions
Click + and link the above action profiles in the following sequence
-
- Modify MARC Bib
- Create Instance
- Create Holdings
- Create Item
10. Upload a valid MARC file
11. Go to Actions/Run and then confirm that you want to run the import using the job profile that was just created
12. Wait till the file is imported
13. Go to Settings/Data EXPORT/Field mapping profile and create the following Field mapping profile:
-
- Name: a unique name
- Output format: MARC
- FOLIO record type: choose Source record storage, Holdings, Item
- Click Add transformations
- In Search and filter, type HRID and press Enter
- Mark the box next to Holdings HRID and add
- the following in the 4 transformation boxes: 901 [blank] [blank] $h
-
- Mark the box next to Item HRID and add
- the following in the 4 transformation boxes: 902 [blank] [blank] $i
-
- Click Save and close, to close the transformations box
- Click Save and close to save the new export field mapping
14. Go to Settings/Data export/Job profile and create the following:
-
- Name: a unique name
- Mapping profile: Select the one created in step 15
Save and close
15. Go to Inventory and do the following search:
-
- Click the search options and select Subject
- Type: Test update
Press Enter
16. Click Actions/Save UUIDs
17. Go to Data Export, and upload the CSV file. Once uploaded, select the job profile created in Step 16. If there is a modal asking whether you want to run for Instances or Holdings, select Instances (this modal appears as of Lotus)
18. Click on the file name at the top of the Export list
19. Go to Settings/Data Import/Field mapping profiles, and Create a field mapping profile with attributes:
-
- Unique valid name
- Incoming record type: MARC Bibliographic
- FOLIO Record type: Instance
- Cataloged date - ###TODAY###
- Instance status term -- "Batch Loaded"
*Statistical codes - Add these to existing and add a statistical code
20. Create a field mapping profile with attributes:
-
- Unique valid name
- Incoming record type: MARC Bibliographic
- FOLIO Record type: Holdings
- Holdings type - "electronic"
- Permanent location - "Online (E)"
- Call number type - "Library of Congress classification"
- Call number - 050$a " " 050$b
- Electronic access - Add these to existing - Relationship - "Resource" - URI - 856$u
21. Create a field mapping profile with attributes:
-
- Unique valid name
- Incoming record type: MARC Bibliographic
- FOLIO Record type: item
- Material type - "electronic resource",
- Item notes - Add these to existing - Note type - "Electronic bookplate" - Note - "Smith Family Foundation" - Staff only - Mark for all affected records
- Permanent loan type - "Can circulate"
- Status - "Available
22. Create an action profile for Instance update.
Link a profile with mapping profile from step#19
23. Create an action profile for Holding update.
Link a profile with mapping profile from step#20
24. Create an action profile for Item update.
Link a profile with mapping profile from step#21
25. Build match profiles: MARC-to-MARC 001 to 001
26. Build match profiles: MARC-to-Holdings 901h to Holdings HRID
27. Build match profiles: MARC-to-Item 902i to Item HRID
28. Create a new "Job profile" with a unique valid name in it.
All other fields should be filled according to pre-conditions
Link in this sequence:
-
- Match profile: 001 to 001
- For matches: Action profile: Update instance
-
- Match profile: MARC-to-Holdings match
- For matches: Action profile: Update holdings
-
- Match profile: MARC-to-Item match
- For matches: Action profile: Update item
Save the job profile
29. Go to the Data Import app, and upload the file that was exported in Step 18
30. Run an import of the exported file, using the update job profile created in Step 28
31. Check log files to see the record with the upload result
32. Pay attention to the status of Instance.
Expected Results: The status of Instance record is updated on the individual logs after uploading MARC file for update .
Actual Results: The status of Instance is Multiple in the Import log after uploading MARC file for update.
TestRail: Results
Attachments
Issue Links
- blocks
-
MODSOURMAN-902 Release v3.5.2 (R3 Nolana Bugfix)
-
- Closed
-
- defines
-
UXPROD-3576 NFR: Data Import Support Bug work (Nolana R3 2022)
-
- Closed
-
- is duplicated by
-
UIDATIMP-1336 Morning Glory: Data Import Summary in Log Inaccurate and Hyperlinks Missing
-
- Closed
-
- relates to
-
MODDATAIMP-744 SPIKE: Design approach for differentiating incoming MARC Bibs that should/shouldn't be saved in SRS
-
- Closed
-
-
MODDICORE-248 MARC field protections apply to MARC modifications of incoming records when they should not
-
- Closed
-
-
MODSOURMAN-817 The status of SRS MARC is not updated in the Import log after uploading MARC file for update
-
- Closed
-
-
MODSOURMAN-901 Improve mechanism for handling "Multiple" status for Instance in case 'Modify' Marc_BIB action was after 'Create' Instance action
-
- Closed
-
-
MODSOURCE-549 Log details for updated are not correct - DRAFT
-
- Closed
-
-
MODSOURMAN-957 The '1' number of SRS MARC and Instance are displayed in cells in the row with the 'Updated' row header at the individual import job's log
-
- Closed
-
- to be improved by
-
MODDATAIMP-744 SPIKE: Design approach for differentiating incoming MARC Bibs that should/shouldn't be saved in SRS
-
- Closed
-
- mentioned in
-
Page Loading...