Logical Keys for Monitoring Plan Import #6894
Description
Created from research ticket #6872. Below is a list of the logical keys that should be used when a monitoring plan is imported to prevent duplicate records from being created:
| Record Type | Logical Keys |
|---|---|
| Defaults | MON_LOC_ID, PARAMETER_CD, DEFAULT_PURPOSE_CD, FUEL_CD, OPERATING_CONDITION_CD, BEGIN_DATE, BEGIN_HOUR |
| Formulas | MON_LOC_ID, FORMULA_IDENTIFIER |
| Loads | MON_LOC_ID, BEGIN_DATE, BEGIN_HOUR |
| Location Attributes | MON_LOC_ID, BEGIN_DATE |
| Methods | MON_LOC_ID, PARAMETER_CD, BEGIN_DATE, BEGIN_HOUR |
| Systems | MON_LOC_ID, SYSTEM_IDENTIFIER |
| System Components | MON_SYS_ID, COMPONENT_ID, BEGIN_DATE, BEGIN_HOUR |
| Analyzer Range | COMPONENT_ID, BEGIN_DATE, BEGIN_HOUR |
| System Fuel Flow | MON_SYS_ID, BEGIN_DATE, BEGIN_HOUR |
| Qualifications | MON_LOC_ID, QUAL_TYPE_CD, BEGIN_DATE |
| Qualification Percent Record | MON_QUAL_ID, QUAL_YEAR |
| Qualification LME Record | MON_QUAL_ID, QUAL_YEAR |
| Qualification LEE Record | MON_QUAL_ID, QUAL_TEST_DATE |
| Span | MON_LOC_ID, COMPONENT_TYPE_CD, SPAN_SCALE_CD, BEGIN_DATE, BEGIN_HOUR |
| Rectangular Duct WAF | MON_LOC_ID, WAF_EFFECTIVE_DATE, WAF_EFFECTIVE_HOUR |
| Loads | MON_LOC_ID, BEGIN_DATE, BEGIN_HOUR |
| Supplemental MATS Method | MON_LOC_ID, MATS_METHOD_PARAMETER_CD, BEGIN_DATE, BEGIN_HOUR |
| Unit Control | UNIT_ID, CE_PARAM, CONTROL_CD, INSTALL_DATE |
| Unit Fuels | UNIT_ID, FUEL_CD, BEGIN_DATE |
| Unit Capacities | UNIT_ID, BEGIN_DATE |
Acceptance Criteria
- The system must not create a duplicate record when importing a JSON file with an end date/time for an existing record. Instead, the original record must be properly ended using the end date/time provided in the JSON import.
- If no matching record is found, a new record must be inserted.
- If a match is found, the existing record must be updated.
- All JSON import scenarios (with and without end date/time) must be thoroughly tested for each applicable data category to verify correct update/insert behavior.