Migration Tools (UXPROD-850)

[UXPROD-1505] Clear all existing data for iterative migration loading Created: 28/Jan/19  Updated: 03/May/21

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Migration Tools

Type: New Feature Priority: P3
Reporter: patty.wanninger Assignee: Ian Walls
Resolution: Unresolved Votes: 0
Labels: po-mvp, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Potential Workaround: Allow direct database access during migration process to TRUNCATE tables at will. -Ian W
Epic Link: Migration Tools
Front End Estimate: Small < 3 days
Front End Estimator: Hkaplanian
Front-End Confidence factor: Low
Back End Estimate: Medium < 5 days
Back End Estimator: Hkaplanian
Development Team: None
Kiwi Planning Points (DO NOT CHANGE): 5
PO Rank: 90
PO Ranking Note: Necessary for developing data-importer tools iteratively. Depends on there actually being data in the system, though (UXPROD-559 and UXPROD-558, to name a couple)
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R1
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: Leipzig (Full TBD): R1
Rank: Leipzig (ERM Aut 2019): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R5

 Description   

In order to test and re-test migration, we need a mechanism to clear existing data in FOLIO to perform fresh loads, as well as be able to add to data already loaded.



 Comments   
Comment by Anya [ 29/Mar/19 ]

Comment from the March Meeting : would this be disabled after a library goes live?

Comment by Ian Walls [ 29/Jul/19 ]

This function would need to be permission-locked aggressively. It may have utility after go-live, but it would be limited and done only extreme circumstances.

Comment by Ian Walls [ 30/Jul/19 ]

Apologies; misunderstood the order of PO ranks. Re-ranking

Comment by Holly Mistlebauer [ 23/Sep/19 ]

Holly removed cap-mvp label per CP team.

Comment by Jenn Colt [ 25/Sep/19 ]

Marking not needed with the understanding that a data upgrade path will be forthcoming and that in the meantime we're wiping/copying with our tools.

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