Remove DWMRCLLRWUMillFacilities from SGID

[stdavis]

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 harvested from is going away. They don't know where the new data is or who maintains it. They do have items in their document management system that link to the data. DEQ decided to migrate this data to their AGOL org. There is no plan for maintenance in the future since they don't know who maintained it in the past. Michelle Horning is the one who created the AGOL items and can be used as a resource for questions about this dataset.

Related Issues

#359
#360

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 (name, completed: 2024/00/00)

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.AGOLItems table (@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 Authoritative field to d in SGID.META.AGOLItems to automatically set the Deprecated AGOL flag. Allow the d to 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:
    • Remove the row from the SGID.META.AGOLItems table. This will trigger the removal of this item in Open SGID (name, completed: 2024/00/00)
    • Unshare the item from its SGID group, which will remove it from the SGID on ArcGIS (name, completed: 2024/00/00)
• 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: 2024/00/00).

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 (name, completed: 2024/00/00)
  • Deprecated database layers should be backed up on Google Drive > AGRC Projects > SGID > deprecated layers > internal_db_sgid_layers (name, completed: 2024/00/00).
• Remove ArcGIS Online item: (name, completed: 2024/00/00)
  • Manually delete the AGOL item
  • -OR-
  • Unshare by changing the AGOL_ITEM_ID field in SGID.META.AGOLItems to 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 from SGID.META.AGOLItems to the AGOLItems_shelved table in AGOL and changing the AGOL_ITEM_ID field in SGID.META.AGOLItems to shelved or 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"
  • Point '"itemId" field to '2c81695cbc644afdba7687e0340b5763'? (@eneemann, completed: 2024/00/00)
  • Change "indexStatus" to "live"? (@eneemann, completed: 2024/00/00)
• Update relevant gis.utah.gov data pages (including downloadMetadata.ts) (name, completed: 2024/00/00)
• Update SGID.META.AGOLItems table (name, completed: 2024/00/00)
  • cut and paste row to AGOLItems_shelved table if shelving (see below)
  • set the AGOL_ITEM_ID field to hosted by <agency> for Farm from AGOL
  • set the AGOL_ITEM_ID field to exclude from AGOL to not publish to ArcGIS Online
• Delete Google Drive data (name, completed: 2024/00/00)
• Remove row from SGID.META.ChangeDetection (name, completed: 2024/00/00)
• Remove data from forklift hashing and receiving (name, completed: 2024/00/00)
• Remove row from data/hashed/changedetection.gdb/TableHashes (name, completed: 2024/00/00)

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

1. Assign yourself or someone to check the item by replacing name with their github @name.
2. Check [x] the box and add the date of verification 2020/01/01 when the task is verified.
3. Strike out all items that do not apply.

• Remove data from Open SGID (name on 2024/00/00)
• sgid-index (@steveoh on 2024/00/00)
• Auditor sets appropriate shelved/static/Deprecated information (@jacobdadams on 2024/00/00)

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

• Twitter (@steveoh)

Group Task Assignments

1. Check [x] the box when you have assigned all the tasks relevant to your group.

• Data Team (@eneemann)
• Dev Team (@steveoh)
• Cadastre Team (@rkelson)

[steveoh]

we're going to hold off on these until we have a new data coordinator to help shape the decisions that are required to proceed.

[eneemann]

@stdavis I'll look closer at these issues in the next few days when I can edit the META table an internal SGID data layers. However, I don't see a matching name or AGOL ID in the SGID Index for this one.

[stdavis]

This may not be in the index. I don't know that we have every dataset in internal in the index.

[steveoh]

In an ideal situation, all SGID data would exist in the sgid index. Even the deprecated datasets. There are many benefits to being complete but in this situation conductor can't do it's checks without the metadata.

[agrc-conductor]

conductor results for tasks - 361

check	status
@steveoh has completed 0 out of 3 tasks	⛔
@jacobdadams has completed 0 out of 1 tasks	⛔
@eneemann has completed 0 out of 2 tasks	⛔
rkelson has completed 1 out of 1 tasks	👍

[agrc-conductor]

conductor results for environment.DWMRCLLRWUMillFacilities

check	status
internal sgid	⛔
meta table	⛔
open sgid	⛔
open data	⛔
arcgis online	⛔
stewardship	⛔ Did not find environment.DWMRCLLRWUMillFacilities in the worksheet