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

[UXPROD-3556] Data Import: Ability to import Data Import profile details via API Created: 11/Feb/22  Updated: 05/Feb/24

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: Ramsons (R2 2024)
Parent: Batch Importer (Bib/Acq)

Type: New Feature Priority: P2
Reporter: Ann-Marie Breaux (Inactive) Assignee: Ryan Taylor
Resolution: Unresolved Votes: 0
Labels: data-import, epam-folijet, quesnelia-stretch
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File UXPROD-3556.png    
Issue links:
Defines
is defined by MODDICONV-284 Define Mapping Field Origins Open
is defined by MODDICONV-285 Job Profile Validation Open
is defined by MODDICONV-286 Allow Job Profiles To Be Imported Open
is defined by MODDICONV-341 Mapping Profile Validation Open
is defined by MODDICONV-342 Action Profile Validation Open
is defined by MODDICONV-343 Match Profile Validation Open
is defined by MODEXPW-211 "A job instance already exists" erro... Closed
is defined by MODDICONV-290 Data Import field mapping profile is ... Blocked
Gantt End to Start
has to be done after MODDATAIMP-577 SPIKE: Design an approach to export/i... Closed
Relates
relates to UXPROD-4348 Data Import: Ability to export Data i... Open
relates to UXPROD-2099 Data Import: Ability to export Data I... Draft
Release: Ramsons (R2 2024)
Epic Link: Batch Importer (Bib/Acq)
Front End Estimate: Out of scope
Front End Estimator: Olamide Kolawole
Front-End Confidence factor: 90%
Back End Estimate: XL < 15 days
Back End Estimator: Olamide Kolawole
Back-End Confidence factor: 80%
Development Team: Folijet
PO Rank: 121
Rank: Cornell (Full Sum 2021): R3

 Description   

Current situation or problem:
This follows UXPROD-4348 Open . Today, there is no ability to easily import Data Import Profile details. Creating data import profiles over and over again in new environments can be tiresome. Plus, if a profile is complicated, it's easier to import it to a new tenant that to recreate it by hand. This functionality will allow administrators to easily import job profiles from other institutions. 

In scope:
API calls to import DI Profile details.

Out of scope:
Front end UI option

Use case(s):

  • Library wants to move import profiles from their sandbox/test tenant to their production tenant
  • Library A wants to use a profile created by Library B
  • PTF, Dev Team, PO wants to store profiles outside of FOLIO, so that they can be added to a new environment for testing

Proposed solution/stories:
Ability to import Data Import Job profiles, including all linked Match, Action, and Field Mapping profile(s) via API. This feature will focus on API support with future release support for a front-end action.

Links to additional info:

Questions:
What to do about reference data that will vary from one tenant to another, e.g. locations, vendors

Further notes:

  • Do export/import via API for first iteration, then add UI option as second iteration

Generated at Fri Feb 09 00:32:57 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.