For the Sept 04-05 data cleaning push, we have the final following data issues to go through by hand:
Current Dens layer
[x] Delete records where Den ID == DELETE (5 records)
[ ] Resolve duplicated 'SAN_FishermanRiver_1' Den Id (in progress)
Field Visits layer
[x] Delete records where Den ID == DELETE (4 records)
[ ] Sort out duplicate Sample IDs
[ ] 'ADA_EveRiver_1_20240816'
[ ] 'LOW_YakounRiver_2_20220907'
[ ] 'SKI_SouthBay_1_20220812'
[ ] 'TLE_FeatherLake_3_20220809'
[x] Sort out the psuedo duplicate issue with 'SKI_DeenaCreek_2_20240609' vs 'DUPLICATE DELETE SKI_DeenaCreek_2_20240609' - it says it's a duplicate, but the information in the other columns is clearly NOT duplicated
[ ] Three dens where the historical data looks very funky and needs to be looked over by Mary
[ ] 'NAH_NahmintRiverNorth_2'
[ ] 'SAN_RonningCreek_2'
[ ] 'TSI_TlatlosCreek_2'
Potential Dens
[ ] Delete records where BCGov Den Name == 'DELETE'
[ ] Check 32 records that have the status of "Den -- Assessed" but BCGov Den Name is NULL (perhaps worth moving to a separate ticket?)
For the Sept 04-05 data cleaning push, we have the final following data issues to go through by hand:
Current Dens layer
Den ID == DELETE(5 records)Field Visits layer
Den ID == DELETE(4 records)Potential Dens
BCGov Den Name == 'DELETE'BCGov Den Name is NULL(perhaps worth moving to a separate ticket?)