What we’re after
With new cycle 2025_2026 partition for tables disclosure.fec_fitem_sched_a/b for the new cyclde (disclosure.fec_fitem_sched_a/b_2027_2028). The tables were already created when encountered the incoming data for cycle 2027/2028 so we will not miss any incoming data. However, official migration script is need to add these to the version controlled base of the database structure.
Related ticket(s)
(Include the tickets that either came before, after, or are happening in tandem with this new ticket)
Action item(s)
(These are the smaller tasks that should happen in order to complete this work)
Completion criteria
(What does the end state look like - as long as this task(s) is done, this work is complete)
References/resources/technical considerations
(Is there sample code or a screenshot you can include to highlight a particular issue? Here is where you reinforce why this work is important)
What we’re after
With new cycle 2025_2026 partition for tables disclosure.fec_fitem_sched_a/b for the new cyclde (disclosure.fec_fitem_sched_a/b_2027_2028). The tables were already created when encountered the incoming data for cycle 2027/2028 so we will not miss any incoming data. However, official migration script is need to add these to the version controlled base of the database structure.
Related ticket(s)
(Include the tickets that either came before, after, or are happening in tandem with this new ticket)
Action item(s)
(These are the smaller tasks that should happen in order to complete this work)
Completion criteria
(What does the end state look like - as long as this task(s) is done, this work is complete)
References/resources/technical considerations
(Is there sample code or a screenshot you can include to highlight a particular issue? Here is where you reinforce why this work is important)