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

[UXPROD-4348] Data Import: Ability to export Data import profile details via API Created: 13/Jun/23  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: Khalilah Gambrell 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-4348.png    
Issue links:
Continues
is continued by MODDATAIMP-577 SPIKE: Design an approach to export/i... Closed
Defines
defines UXPROD-47 Batch Importer (Bib/Acq) Analysis Complete
Relates
relates to UXPROD-2099 Data Import: Ability to export Data I... Draft
relates to UXPROD-3556 Data Import: Ability to import Data I... Open
Release: Ramsons (R2 2024)
Epic Link: Batch Importer (Bib/Acq)
Front End Estimate: Out of scope
Front End Estimator: Ryan Taylor
Front-End Confidence factor: 100%
Back End Estimate: Medium < 5 days
Back End Estimator: Kateryna Senchenko
Back-End Confidence factor: 90%
Development Team: Folijet
PO Rank: 122

 Description   

Current situation or problem:
Today, there is no ability to easily export Data Import Profile details. This functionality will allow administrators to easily review Job Profile setup details and share with other institutions. 

In scope:
API calls to retrieve DI Profile details.

Out of scope:
Front end UI option (see UXPROD-2099 Draft )

Use case(s):

  • Exporting profiles for review in support of troubleshooting.
  • Sharing of DI profiles across users/institutions.

Proposed solution/stories:
Ability to export 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:

  • UXPROD-3556 Open Data Import: Ability to import Data Import profile details via API (sibling feature)

Questions:
Any response limitations to consider

Technical notes:
As a system administrator
I want to export a data import job profile including all linked match profile(s)/action profile(s)/field mapping profile(s) via API
So that I can review setup and share with other institutions 

  • API support is required - a single response must return the job profile and all linked match/action/field mapping profiles
    • Must account for nested match profiles 
    • Must account for nest action profiles 
  • Can get job profile and linked profiles details by
    • job profile UUID
    • OR by query by job profile name/match profile/action profile/field mapping profile or created date value or last updated value 
      • Support sort parameter by job profile name (A-Z) or by last updated value (descending order)
      • Assume query can support returning all profiles that match query 
  • Do not return any profile details whereby showHidden = true (https://folio-org.atlassian.net/browse/MODDICONV-234)
  • The response should support the user's ability to import profile details so that the user can use the job and linked match/action/field mapping profiles in another template 

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