Monitoring Plan Schema Issue - unitControlData

[maheese]

• [ ] Investigate to see if we change the data type VARCHAR to numeric resolves this
• [ ] Schema, DTO, and database will be made if proof of concept is successful

Developer Notes:

1. Changing the type from varchar to "indicator" should also include JSON and database name changes to be consistent.
2. The change to originalCode in the JSON should include changing the name to originalIndicator or originalControlIndicator.
3. According to a later comment, the JSON OS field is seasonalControlsIndicator. "Seasonal" does not indicate Ozone Season and the field will be an indicator. So the name should be either osControlIndicator or seasonControlIndicator.
4. The database names should also change from ORIG_CD and SEAS_CD to ORIG_IND and SEAS_IND or maybe ORIGINAL_CONTROL_IND and OS_CONTROL_IND (or SEASON_CONTROL_IND).
5. The changes will involve Infomatica changes or potentially deployment changes to handle the name and type changes.
6. The changes will likely involve check changes based on the type and name changes.
7. And to explicitly state it, the changes will involve JSON export, JSON import, and Official import changes and testing.
8. CAMD needs to indicate whether to pursue these changes. We would need to make these changes now or never.

[maheese]

In element unitControlData of the monitoring plan the properties originalCode and seasonalControlsIndicator are "indicators" and defined as strings with enumerated values null, “0”, and “1”. Other similar “indicator” fields are numeric with values null, 0, and 1. These fields need to be made consistent with the other indicator fields used in the schema.

This issue was reported by an industry user in Request Tracker ticket 73082

[acollad1]

CVP confirms that there are strings in the database so we would not be able to make them consistent. They are exceptions.

[acollad1]

On DSU 11/22 it was determined that EPA POs need further discussion on this before an action is taken

[acollad1]

Jason to reach out to Dwayne to confirm that the proposed changes won't affect their work

[annalbrecht]

Verify if this needs to be changed.

[maheese]

@djw4erg thanks for looking into this. Since this is not show stopper we decided not to work on this for phase 1.