Is PrimaryUseCategoryCV in timeseries data suppose to act like BeneficialUseCategory?

[rwjam]

Not sure if intentional, but the PrimaryUseCategoryCV field in the SiteVariableAmounts_fact table for site-specefic time series data has the same CV checks and balances as a BeneficialUseCategory does. Meaning any entry into PrimaryUseCategoryCV has to be in the CVs.BeneficialUses table.

Wasn't the intended use of PrimaryUseCategoryCV for SiteVariableAmounts_fact have it act the same way as PrimaryBeneficialUseCategory does for the AllocationAmounts_fact table?

• Side Note: It's not shown in the figure, but BeneficialUseCategory is mandatory for our WaDE Uploader scripts in order to input data into the SiteVariableAmounts_fact table (this is due to the 1-M relationship we have in our schema with the timeseries data).

[rwjam]

For a temp fix, we will add the WaDE Name entries (the stuff we use to assign a value to the PrimaryUseCategoryCV column) into the CV.BeneficialUseCategory as a new category / row entry. This will allow us to continue to work with timeseries data and have it behave as intended.

We will try and get DPL / Nathan to take a look at this in the future when funding is available.