Batch Importer (Bib/Acq)
(UXPROD-47)
|
|
| Status: | Closed |
| Project: | mod-di-converter-storage |
| Components: | None |
| Affects versions: | None |
| Fix versions: | 2.1.0 | Parent: | Batch Importer (Bib/Acq) |
| Type: | Bug | Priority: | P2 |
| Reporter: | Christie Thomas | Assignee: | Volodymyr Rohach |
| Resolution: | Done | Votes: | 0 |
| Labels: | architectural, arlef-di, data-import, epam-folijet, folidemo166-167, folijet-olamide, has-testrail, support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Folijet Sprint 166, Folijet Sprint 167 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Story Points: | 1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Folijet | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Release: | Poppy (R2 2023) | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| CSP Approved: | Yes | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| CSP Request Details: | Nolana/Orchid CSP requested 21 June 2023
Approved 22 June 2023 by Khalilah, Mike G, Kristin M, Mark V, Debra H, Harry K |
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Potential Workaround: | Work includes creating new match profiles with the same match point but a different name. This is the work around that worked until Nolana when only the primary match point had to be unique, but after Nolana even sub-matches must be unique profiles. | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Affected Institution: |
!!!ALL!!!, University of Chicago
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Batch Importer (Bib/Acq) | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| RCA Group: | Incomplete/missing requirements | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Affected releases: |
Orchid (R1 2023), Nolana (R3 2022)
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
Overview: Data import job profiles can be created using the same match profiles more than once, but once the job profile is saved the reused components are repeated under each section. For instance, Chicago needs to create a job profile that matches the 035$z of the incoming record to the OCLC number in the instance, then submatch to the instance status is equal to a constant value (e.g., Batch Loaded), and then submatch to the holdings type (e.g., Electronic). If there is not match on the 035$z to the OCLC number, then the import should match the 035$a of the incoming record to the OCLC number in the instance record with an instance submatch where the instance status is equal to a constant value and the holdings type is equal to a constant value. The submatches are the same for each of the components. This is not currently possible without creating unique match profile for each time a match is needed to be used in an import job profile. This bug does not require importing anything, only building the various profiles and assembling the job profile Steps to Reproduce:
Expected Results: I expect to see a job profile that will match the 035$z to Instance OCLC number, instance status, and holdings type then update the instance and and the holdings if it is a match. If there is no match I expect to see a match on the 035$a to the instance OCLC number, then submatches to the instance status and holdings type with update actions taken if there is a match. I expect to be able to build complex matches that re-use match profiles within a single job import profile. Actual Results: Each primary match 035$z to OCLC and 035$a to OCLC each contain two matches to holdings type and each holding type electronic match contains two update instance and two update holdings actions. Additional Information: This behavior is present in Nolana and FOLIO snapshot. Interested parties: University of Chicago
BE Notes:
ORCHID Critical service patch details
NOLANA Critical service patch details
|
| Comments |
| Comment by Ann-Marie Breaux (Inactive) [ 08/Mar/23 ] |
|
Hi Christie Thomas I was definitely able to reproduce this on Snapshot. Thank you for writing it up! Mariia Aloshyna and Kateryna Senchenko please review. Per Christie, we've made the work-around more of a headache as of Nolana. Is there any simple way we can allow the same match and action profiles to be used more than once in a job profile, without having to duplicate the match/action profiles and give them different names? |
| Comment by Ann-Marie Breaux (Inactive) [ 30/Mar/23 ] |
|
Ann-Marie Breaux Add something on the wiki that the same match/action/field mapping profile can be used more than once in a job profile (in tips and tricks or in Folijet dev reqs area) |
| Comment by Ann-Marie Breaux (Inactive) [ 05/Apr/23 ] |
|
Folijet refinement: BE needs to review more and discuss. Also consider whether it could be released as a Nolana and/or Orchid patch, depending on the complexity and risk |
| Comment by Jenn Colt [ 10/Apr/23 ] |
|
As we work more in Nolana I find we are encountering more and more of the same problems Christie has. I used to be able to create two checks for matches and have each branch end in a create if there is no match and now I can't. I didn't realize that was what the problem was because the profile saved with no problem it was only after I went back and looked at it that I realized it had removed the duplicated actions with no warning at all. This will mean increasing even further the number of profiles that we have. |
| Comment by Ann-Marie Breaux (Inactive) [ 11/Apr/23 ] |
|
Hi Jenn Colt I'm really sorry to see that. We'll try to pull this bug into the current sprint and work on it ASAP. Has this caused profiles that worked for you in Morning Glory to no longer work in Nolana? If so, it sounds like we should also consider a patch for Nolana and Orchid. On Orchid bugfest, would it be possible to create a sample profile that worked previously, but is no longer working, and attach a relevant file to this bug? Thank you so much |
| Comment by Maksym Ishchenko [ 13/Apr/23 ] |
|
Hello Ann-Marie Breaux Could you create scenarios for the 2nd and 3rd "Checks" in BE notes and for Edits and Duplicates scenarious? |
| Comment by Maksym Ishchenko [ 07/Jun/23 ] |
|
This ticket was checked on snapshot env. No additional profiles are appears now when creating/duplicating/editing job profiles with repeatable match/action profiles. Moving issue to In review column |
| Comment by Ann-Marie Breaux (Inactive) [ 19/Jun/23 ] |
|
Thanks, Maksym Ishchenko Looks good to me also. Thank you for the work, Volodymyr Rohach Christie Thomas and Jenn Colt Please give this a try on Snapshot when you have a chance. The current solution (which we'll aim to backport to Orchid and possibly Nolana) should resolve the type of profile that Christie has outlined. Per the developers, the described case will be covered, but in case different building blocks would be required using same associations, we still might run into a problem. And in Poppy, we will implement a long-term solution that will resolve it despite different associations. However, the developers deem that fix as too risky to backport to Orchid or Nolana. |