-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Summary
- Internal Dataset Name: SGID.ENVIRONMENT.DWMRCLLRWUMillFacilities
- External Dataset Name: Utah DWMRC Low Level Waste Disposal and Uranium Mill Facilities
- ArcGIS Online Url: https://www.arcgis.com/home/item.html?id=2c81695cbc644afdba7687e0340b5763
The old DEQ Oracle database that housed the view that this data was migrated to Salesforce. The new AGOL layer loaded by Michelle is a copy of the old SGID data sourced from the Oracle DB. While we could wire up a connection to their new data source in Salesforce, they anticipate very few (if any) changes to this data, so we decided to just use Michelle's AGOL layer. She'll update it manually if any changes need to be made.
Related Issues
Migration Guide
This dataset has been replaced by this DEQ AGOL Service.
Action items
These questions and action items should be addressed before any further actions are taken.
- Should the new DEQ AGOL item be included in SGID on ArcGIS? - yes (@eneemann)
- Should the new DEQ AGOL item be included in the SGID Index? - yes (@eneemann)
- Work with Michelle Horning to get this AGOL item standardized and shared to our Hub (@eneemann, completed: 2025/02/26)
Soft Delete
The purpose of the soft delete is to ensure that all of our users and applications have gracefully migrated off of the dataset. Soft deletes will remain in effect for 14 days. During this time, we will have the ability to restore the dataset to its original SGID offering(s). After these 14 days, the item is then ready for a hard delete.
Note: If this dataset is being replaced, then wait until the new data is publicly available before completing these steps:
- Append "(Mature Support)" to the end of the item title in the
SGID.META.AGOLItemstable (@eneemann, completed:2024/12/23) - Remove all tags other than "Deprecated" in the SDE metadata (@eneemann, completed:
2024/12/23) - Add note to SDE description noting when layer will be deleted and any replacement layer (@eneemann, completed:
2024/12/23) - Update the SGID Index row as deprecated by pasting the related Porter issue URL in the "porterUrl" field and setting the value of the "indexStatus" field as "removed". Also update the "refreshCycle" field (@eneemann, completed:
2024/12/23) - Change
Authoritativefield todinSGID.META.AGOLItemsto automatically set theDeprecatedAGOL flag. Allow thedto persist through one run of Auditor - currently, Auditor runs daily at 5:00am (name, completed:2024/12/23)- After at least one successful run of Auditor:
- Check if this layer in the base maps. If so, work with Zach to develop a path forward before you proceed with a Hard Delete (@ZachBeck , completed:
2025/01/13).
Hard Delete
Target Date: 2025/01/20
Hard deletes are final. It is recommended to complete the soft delete process before moving on to these steps. If you decide to skip the soft delete, note that you will need to incorporate some of those steps here.
- Manually remove data from the Internal SGID (@ZachBeck, completed:
2025/01/29)- Deprecated database layers should be backed up on Google Drive > AGRC Projects > SGID > deprecated layers > internal_db_sgid_layers (@ZachBeck, completed:
2025/01/29).
- Deprecated database layers should be backed up on Google Drive > AGRC Projects > SGID > deprecated layers > internal_db_sgid_layers (@ZachBeck, completed:
- Remove ArcGIS Online item: (@ZachBeck, completed:
2025/01/29)- Manually delete the AGOL item
- Deprecated AGOL items can be backed up on Google Drive > AGRC Projects > SGID > deprecated layers > agol_sgid_layers.
- [ ] Remove Farm from AGOL connection (name, completed:2024/00/00)
- Update the SGID Index fields: "arcGisOnline", "openSgid", "openSgidTableName" for new DEQ data hosted in AGOL
- Update relevant gis.utah.gov data pages (including
downloadMetadata.ts) (@eneemann, completed:2025/02/27) see PR #2967
- [ ] UpdateSGID.META.AGOLItemstable (@eneemann, completed:2024/00/00)
- cut and paste row toAGOLItems_shelvedtable if shelving (see below)
- set theAGOL_ITEM_IDfield tohosted by <agency>for Farm from AGOL
- set theAGOL_ITEM_IDfield toexclude from AGOLto not publish to ArcGIS Online
- [ ] Delete Google Drive data (name, completed:2024/00/00) - Remove row from
SGID.META.ChangeDetection(@stdavis, completed:2024/02/03)- It was already gone.
- Remove data from forklift hashing and receiving (@stdavis, completed:
2024/02/03) - Remove row from
data/hashed/changedetection.gdb/TableHashes(@stdavis, completed:2024/02/03)
Shelve/Static
Choose one based on situation.
- [ ] Upload to UtahAGRC/AGRC_Shelved folder in AGOL (New shelved item not already in AGOL) (name, completed: 2024/00/00)
- [ ] Move existing AGOL item to AGRC_Shelved AGOL folder (shelving an item already in AGOL) (name, completed: 2024/00/00)
- [ ] Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for static datasets) (name, completed: 2024/00/00)
Add record to table.
- [ ] Add record to AGOLItems_shelved table in ArcGIS Online with shelved or static in the CATEGORY field (@eneemann, completed: 2024/00/00)
🤖 Automation validation
- Assign yourself or someone to check the item by replacing
namewith their github@name. - Check [x] the box and add the date of verification
2020/01/01when the task is verified. Strikeout all items that do not apply.
- Remove data from Open SGID (@steveoh on
2025/02/27) - sgid-index (@steveoh on
2025/02/27) - Auditor sets appropriate
shelved/static/Deprecatedinformation (@jacobdadams on2024/12/30)
Are there service dependencies
- Are clients querying this data with the WebAPI? This dashboard may be helpful.
- Notify Don Jackson (don.jackson1 at motorolasolutions.com) if the data is in the Next-Generation 911 Motorola Aware Map? - not required (@eneemann on
2024/12/23) - Does any other application depend on this data?
Notification
- [x Twitter (@steveoh)
Group Task Assignments
- Check [x] the box when you have assigned all the tasks relevant to your group.