Migration Tools (UXPROD-850)

[UXPROD-1502] Migration loader performance requirements Created: 28/Jan/19  Updated: 16/Sep/20  Resolved: 13/Jun/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q2 2019
Parent: Migration Tools

Type: New Feature Priority: P3
Reporter: patty.wanninger Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Link: Migration Tools
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
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: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   

1.Loader should be performant, such that it allows for the iteration of a cycle of loading, testing, and correcting of data on a daily basis (around 8 hours for the load).

2. Where needed for performance, loader should be supported by special bulk-processing APIs, which allow for the submission of lists of json objects, and for the processing of those lists in batch.



 Comments   
Comment by Anya [ 29/Mar/19 ]

comment from the March Meeting : Define perf req & confirm FOLIO meets them

Comment by Hkaplanian [ 13/Jun/19 ]

Closing since this is not a feature. This needs to be listed under requirements for the migration loader feature.

Comment by Hkaplanian [ 13/Jun/19 ]

Closing since this is not a feature. This needs to be listed under requirements for the migration loader feature in JIRA. This should not exist on it's own.

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