-
Notifications
You must be signed in to change notification settings - Fork 0
Description
Summary
- Internal Dataset Name: SGID.ENVIRONMENT.DWQMonitoringLocations
- External Dataset Name: Utah DWQ Monitoring Locations
- ArcGIS Online Url: https://www.arcgis.com/home/item.html?id=e3d89f76e52942c2bc76dcec65a435ab
This is part of a group of layers (used in the DEQ Interactive Map) that DWQ has recently moved from File Geodatabases on a network share to AGOL hosted feature layers. This means that we no longer need to pull data from their file share for the interactive map and can instead reference their AGOL items directly. These layer are also currently in SGID. We can now remove them from internal/OpenSGID and our AGOL org and replace them with shared items from DEQ in SGID for ArcGIS.
Migration Guide
This dataset has been replaced by this DEQ AGOL Service.
Action items
These items should be addressed before any further actions are taken.
- Should the new DEQ AGOL item be included in SGID on ArcGIS? Yes via shared items from DEQ
- Should the new DEQ AGOL item be included in the SGID Index? Yes
- Work with Ryan Parker to get his AGOL item standardized and shared to our Hub (@gregbunce, completed:
2024/90/19)
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 (@stdavis, completed:2024/09/30) - Remove all tags other than "Deprecated" in the SDE metadata (@stdavis, completed:
2024/09/30) - Add note to SDE description noting when layer will be deleted and any replacement layer (@stdavis, completed:
2024/09/30) - Update the SGID Index to point to the DEQ AGOL item (@stdavis, completed:
2024/09/30) - Change
Authoritativefield todinSGID.META.AGOLItemsto automatically set theDeprecatedAGOL flag. Allow thedto persist through one run of Auditor - currently, Auditor runs daily at 5:00am (@stdavis, completed:2024/09/30)- After at least one successful run of Auditor:
- Remove the row from the
SGID.META.AGOLItemstable. This will trigger the removal of this item in Open SGID (@stdavis, completed:2024/10/14) - Unshare the item from its SGID group, which will remove it from the SGID on ArcGIS (@stdavis, completed:
2024/10/14)
- [ ] 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 (name, completed:2024/00/00).
- Remove the row from the
- After at least one successful run of Auditor:
Hard Delete
Target Date: 2024/10/15
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:
2024/12/11)- Deprecated database layers should be backed up on Google Drive > AGRC Projects > SGID > deprecated layers > internal_db_sgid_layers (@ZachBeck, completed:
2024/12/11).
- 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:
2024/12/11)- Manually delete the AGOL item
- -OR-
- Unshare by changing theAGOL_ITEM_IDfield inSGID.META.AGOLItemsto something other than an Item ID and manually changing the sharing settings (remove the item from all SGID groups, remove Public sharing), - -OR-
- Shelve the data by copying the row fromSGID.META.AGOLItemsto theAGOLItems_shelvedtable in AGOL and changing theAGOL_ITEM_IDfield inSGID.META.AGOLItemstoshelvedor some other note. - 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" (@stdavis, completed:2024/00/00)
- Update relevant gis.utah.gov data pages (including
downloadMetadata.ts) (@stdavis, completed:2024/10/21)
- [ ] UpdateSGID.META.AGOLItemstable (name, completed:2024/00/00)- cut and paste row to
AGOLItems_shelvedtable if shelving (see below) - set the
AGOL_ITEM_IDfield tohosted by <agency>for Farm from AGOL - set the
AGOL_ITEM_IDfield toexclude from AGOLto not publish to ArcGIS Online
- cut and paste row to
- Delete Google Drive data (@ZachBeck, completed:
2024/12/11) - Remove row from
SGID.META.ChangeDetection(@stdavis, completed:2024/10/21) - Remove data from forklift hashing and receiving (@stdavis, completed:
2024/10/21) - Remove row from
data/hashed/changedetection.gdb/TableHashes(@stdavis, completed:2024/10/21)
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 (name, 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 (@stdavis on
2024/10/21) [ ] sgid-index (@steveoh on2024/00/00)- Auditor sets appropriate
shelved/static/Deprecatedinformation (@jacobdadams on2024/10/01)
Are there service dependencies
- Are clients querying this data with the WebAPI?
No, I checked the dashboard and couldn't find any requests. - Notify Don Jackson (don.jackson1 at motorolasolutions.com) if the data is in the Next-Generation 911 Motorola Aware Map? (@gregbunce on
2024/09/16) - Does any other application depend on this data?
- Enviro, but I've already pointed it at the new AGOL items. There may be some cleanup in forklift at some point but I don't think that it should block this porter item.
Notification
- Twitter (@steveoh)
Group Task Assignments
- Check [x] the box when you have assigned all the tasks relevant to your group.
- Data Team (@gregbunce)
- Dev Team (@steveoh)
- Cadastre Team (@rkelson)