Summary

• Internal Dataset Name: SGID.PLANNING.UtahPLI_Lines_Proposal_Jan16
• External Dataset Name: Utah PLI Lines Proposal Jan16
• ArcGIS Online Url: https://www.arcgis.com/home/item.html?id=b5e4e5236c2e4fe1a575ab5535b44677/

In a recent review of the SGID Index, these apparently duplicate datasets were discovered. PublicLandsInitiativeHR5780Lines_BLM2016 seemed to be the more complete dataset so the decision was made to deprecate UtahPLI_Lines_Proposal_Jan16.

Migration Guide

This dataset has been replaced by (SGID.PLANNING.PublicLandsInitiativeHR5780Lines_BLM2016) which is named (planning.public_lands_initiative_hr5780_lines_blm_2016) in the Open SGID and (Utah Public Lands Initiative HR5780 Lines BLM 2016) in the SGID on ArcGIS.

The replaced data is still accessible via our shelved policy in AGOL (a link to the shelved item).

Action items

1. Assign a person who should complete the task by replacing name with their github @name.
2. Check [x] the box when the task is completed and add the date of completion.
3. Strike out all items that do not apply.

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 (@stdavis, completed: 2024/04/02)
• Remove all tags other than "Deprecated" in the SDE metadata (@stdavis, completed: 2024/00/00)
• Add note to SDE description noting when layer will be deleted and any replacement layer (@stdavis, completed: 2024/04/02)
• Update the SGID Index row as deprecated by pasting the related Porter issue URL in the "porterUrl" field and setting the value of the "ugrcStatus" field as "deprecated" (@stdavis, completed: 2024/04/02)
• 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 (@stdavis, completed: 2024/04/02)
  • 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 (@jacobdadams, completed: 2024/04/05)
    • Unshare the item from its SGID group, which will remove it from the SGID on ArcGIS (@jacobdadams, completed: 2024/04/05)
• 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 (@stdavis, completed: 2024/03/28).

Hard Delete

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.

• Hard delete target date (@gregbunce, set: 2024/04/29)
• Manually remove data from the Internal SGID (@gregbunce, completed: 2024/04/29)
  • Deprecated database layers should be backed up on Google Drive > AGRC Projects > SGID > deprecated layers > internal_db_sgid_layers (@gregbunce, completed: 2024/04/29).
• Remove ArcGIS Online item: (@jacobdadams, completed: 2024/06/17)
  • 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)
    • does not exist
• Update relevant gis.utah.gov data pages (@stdavis, completed: 2024/05/06)
  • could not find any

- [ ] Update SGID.META.AGOLItems table (@stdavis, 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 (@gregbunce, completed: 2024/00/00)

• Remove row from SGID.META.ChangeDetection (@stdavis, completed: 2024/05/13)
• Remove data from forklift hashing and receiving (@stdavis, completed: 2024/05/13)
• Remove row from data/hashed/changedetection.gdb/TableHashes (@stdavis, completed: 2024/05/13)

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) (@jacobdadams, completed: 2024/06/17)
  - [ ] 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 (@jacobdadams, completed: 2024/06/17)

🤖 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 (@stdavis on 2024/05/20)
• sgid-index (@steveoh on 2024/05/30)
• Auditor sets appropriate shelved/static/Deprecated information (@jacobdadams on 2024/04/05)

Are there service dependencies

• Are clients querying this data with the WebAPI?
  - [ ] Notify Don Jackson (don.jackson1 at motorolasolutions.com) if the data is in the Next-Generation 911 Motorola Aware Map? (@gregbunce on 2024/00/00)
• Does any other application depend on this data?
  • Not that I could find in a search on GitHub.

Notification

• Twitter (@steveoh)

Group Task Assignments

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

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