QC stream sites throughout datasets

[ErinCain]

Examples shared from Josh:

Stream and site names are not always consistent across files, and suggest making a stream_site field which concatenates stream and site (e.g., battle creek_ubc) in all standard files. Examples…

a. In jpe_weekly_unmarked_catch.csv Butte Creek sites are adams dam, okie dam 1 and okie dam 2. But in standard_catch.csv and standard_flow.csv there is only adams dam and okie dam. Hoping the two okie dam sites combined in the weekly catch file? b. In jpe_weekly_unmarked_catch.csv the site for Yuba River is yuba river. But in standard_catch.csv Yuba River sites are hallwood and yuba river. In standard_flow.csv for stream=yuba river is yub. In cases where there is one gauge providing discharge measurements for more than one RST site, suggest replicating the data, or we need another table that relates the gauge to each site. Perhaps make all stream and site names lower cases.

Check other datasets to ensure consistency of stream/site throughout

[alvizek]

also noted that battle creek site is "battle creek" in catch and "ubc" in mark/recap