Details
-
New Feature
-
Status: Draft (View Workflow)
-
P2
-
Resolution: Unresolved
-
None
-
None
-
Not Scheduled
-
Folijet
-
-
R3
Description
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.
Use cases:
- 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
In scope:
- Export profiles from a tenant (job, match, action, field mapping) - see UXPROD-2099
- Import profiles to a new tenant (job, match, action, field mapping) - this feature
Questions:
- What to do about reference data that will vary from one tenant to another, e.g. locations, vendors
TestRail: Results
Attachments
Issue Links
- has to be done after
-
MODDATAIMP-577 SPIKE: Design an approach to export/import DI profiles
-
- Closed
-
- is defined by
-
MODDICONV-284 Define Mapping Field Origins
-
- Open
-
-
MODDICONV-285 Job Profile Field Value Validation
-
- Open
-
-
MODDICONV-286 Allow Job Profiles To Be Imported
-
- Open
-
-
MODDICONV-290 Data Import field mapping profile is saved with data deleted from the system
-
- Blocked
-
-
MODEXPW-211 "A job instance already exists" error bulk editing Items on large bulk edit job
-
- Closed
-
- relates to
-
UXPROD-2099 Ability to export Data Import profile details
-
- Draft
-