Skip to content

feature: initiative specific data preparation configuration #226

@jdhoffa

Description

@jdhoffa
          actually, I think we should consider this more... I think it might be prudent to create a new `2023Q4_PA2024CH` config because it's clear that a situation can easily occur where the config for a COP project is different than what we want for `GENERAL`. @jdhoffa can we discuss a strategy for this

Originally posted by @cjyetman in #225 (comment)

There may be situations, for example when running multiple COP projects in a single year, where we may want different data configurations, for the same quarter data, for different initiative codes.

To do this, would require changing the way we structure our config file.

AB#10861

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions