Batch Importer (Bib/Acq) (UXPROD-47)

[UIDATIMP-1521] Not able to use system generated Match profiles Created: 14/Sep/23  Updated: 05/Feb/24

Status: Blocked
Project: ui-data-import
Components: None
Affects versions: None
Fix versions: None
Parent: Batch Importer (Bib/Acq)

Type: Bug Priority: P2
Reporter: Raegan Wiechert Assignee: Ryan Taylor
Resolution: Unresolved Votes: 0
Labels: data-import, discuss-with-subgroup, epam-folijet, known-issue-orchid, known-issue-poppy, needs-points, needs-testrail, support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines UXPROD-2742 MARC-MARC matching enhancements: Narr... In Progress
Relates
relates to UIDATIMP-833 Suppress OCLC Single record import ma... Closed
Sprint:
Development Team: Folijet
Release: Quesnelia (R1 2024)
Affected Institution:
MI State University/Library of Michigan
Epic Link: Batch Importer (Bib/Acq)
RCA Group: Not a bug
Affected releases:
Poppy (R2 2023), Orchid (R1 2023)

 Description   

Overview: I am attempting to create a new job profile for single record import to get rid of the junk fields. I was able to do this a while back on our test tenant and today I was finally able to get around to creating it on our production tenant. However, when I went to add the Match profile (Inventory Single Record - Default match for existing SRS record) which is a system generated profile, it did not appear as one of the options. When I look at the Action profiles, I am able to choose system generated ones, so the problem is only with the Match profiles. We are on Orchid-SP-5. I was also able to recreate the issue on Snapshot. (I don't have Bugfest access so I did not try that.)

Steps to Reproduce:

  1. Log into FOLIO Snapshot
  2. Go to Settings–>Data Import–>Job Profiles–>Actions–>New Job Profile
  3. Under Overview, click on the plus sign
  4. Choose Match

Expected Results: A list of all Match Profiles (both system provided and locally created) is shown

Actual Results: Only locally created Match Profiles are shown (if there are none, you get "no results found")

Additional Information:
When I did my original creation of the job profiles in May, our test tenant would have been on Orchid-SP-3 or 4, so this seems to be something that was introduced in one of the patches since then.

Interested parties:



 Comments   
Comment by Charlotte Whitt [ 18/Sep/23 ]

Support SIG: Ann-Marie Breaux the Support SIG gave this issue the priority P2. It seams this issue has been caused by CSP #5.

Comment by Ann-Marie Breaux (Inactive) [ 19/Sep/23 ]

Mariia Aloshyna Please take a quick look at this bug - can you tell if it was caused by one of the CSPs? It's happening in Poppy as well.

Comment by Mariia Aloshyna [ 21/Sep/23 ]

Hi Ann-Marie Breaux we had a story a while ago to suppress the mentioned match profiles from Job profile create/edit - https://folio-org.atlassian.net/browse/UIDATIMP-833
This is not a bug

Comment by Raegan Wiechert [ 21/Sep/23 ]

Hmmm.....well I would like this to be reconsidered. From the date on UIDATIMP-833 Closed , it was done before we could create our own single-record import profiles, so I don't think the reasoning behind it still exists. And while I guess other people have been successful in making their own match profiles, whenever I made my own, which exactly matched the default or when I just duplicated the default and changed its name, I could not get the job to work. It only worked when I used the default profiles. Which brings me to a second point, if UIDATIMP-833 Closed was done almost three years ago, why was I able to use the default match profiles in our test system?

Comment by Charlotte Whitt [ 20/Nov/23 ]

Support SIG: Ann-Marie Breaux do you need more input from Raegan Wiechert or do you have all the information needed and this ticket is ready to be pulled in to one of the upcoming FOLJIET Sprints?

Comment by Ann-Marie Breaux (Inactive) [ 12/Dec/23 ]

Ryan Taylor maybe reverse the decision from UIDATIMP-833 Closed , and allow the profiles named in it to display, and be duplicated, but NOT be edited or deleted (see action menu on https://folio-snapshot.dev.folio.org/settings/data-import/action-profiles/view/d0ebba8a-2f0f-11eb-adc1-0242ac120002?sort=name as an example). Discuss with subgroup

Comment by Debra Howell [ 08/Jan/24 ]

From SUPPORT SIG: Ryan Taylor This bug is listed as "Blocked." Would you please list the blocking JIRA? Also, the RCA status is "Not a bug." Would you please clarify why this isn't a bug when it is filed by an implemented library? Thanks!

 

Comment by Debra Howell [ 05/Feb/24 ]

From SUPPORT SIG: Ryan Taylor This bug is listed as "Blocked." Would you please list the blocking JIRA? Also, the RCA status is "Not a bug." Would you please clarify why this isn't a bug when it is filed by an implemented library? Thanks!

Generated at Thu Feb 08 22:23:30 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.