Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove DWQAssessmentUnits from SGID #356

Closed
27 tasks done
stdavis opened this issue Oct 1, 2024 · 30 comments
Closed
27 tasks done

Remove DWQAssessmentUnits from SGID #356

stdavis opened this issue Oct 1, 2024 · 30 comments
Labels
deprecation Removing data and or a service porter issue related to adding and removing data and services

Comments

@stdavis
Copy link
Member

stdavis commented Oct 1, 2024

Summary

This is an out-of-date layer that was never cleaned up.

Comments from Mark Stanger on 10/1:

[This layer] is very out-of-date. I recognize assessment units, or the lack thereof, as being several years old. For example, the Great Salt Lake was one assessment unit (AU) but years ago was split into four AUs: Gunnison Bay, Gilbert Bay, Bear River Bay and Farmington Bay.
Another example are the AUs in the Price River area that have an upper elevation boundary of 7200 or 7500 feet, such as Lower Grassy Trail Creek (UT14060007-012). I cannot remember if those specific boundaries were ever finalized/approved.
I'm still looking for the source data that matches Scott's reference, but I am certain it is no longer applicable.

Migration Guide

This dataset has been replaced by Utah Assessed Waters.

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/10/07)
  • Remove all tags other than "Deprecated" in the SDE metadata (@stdavis, completed: 2024/10/07)
  • Add note to SDE description noting when layer will be deleted and any replacement layer (@stdavis, completed: 2024/10/07)
  • 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 "removed". Also update the "refreshCycle" field (@stdavis, completed: 2024/10/07)
  • 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/10/07)
    • 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 (@stdavis, completed: 2024/10/21)
      • Unshare the item from its SGID group, which will remove it from the SGID on ArcGIS (@stdavis, completed: 2024/10/21)
        - [ ] 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).

Hard Delete

Target Date: 2024/10/21

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/16)
    • Deprecated database layers should be backed up on Google Drive > AGRC Projects > SGID > deprecated layers > internal_db_sgid_layers (@ZachBeck, completed: 2024/12/16).
  • Remove ArcGIS Online item: (@ZachBeck, completed: 2024/12/16)
    • 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"(@ZachBeck, completed: 2024/12/16)
  • Update relevant gis.utah.gov data pages (including downloadMetadata.ts) (@stdavis, completed: 2024/10/28)
    - [ ] 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 (@ZachBeck, completed: 2024/12/16)
  • Remove row from SGID.META.ChangeDetection (@stdavis, completed: 2024/10/28)
  • Remove data from forklift hashing and receiving (@stdavis, completed: 2024/10/28)
  • Remove row from data/hashed/changedetection.gdb/TableHashes (@stdavis, completed: 2024/10/28)

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.

Are there service dependencies

Notification

Group Task Assignments

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

I need some help with the shelved tasks. I'm not sure how those are supposed to be done.

@stdavis stdavis added deprecation Removing data and or a service porter issue related to adding and removing data and services labels Oct 1, 2024
@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

stdavis added a commit to agrc/gis.utah.gov that referenced this issue Oct 28, 2024
stdavis added a commit to agrc/gis.utah.gov that referenced this issue Oct 28, 2024
@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@steveoh
Copy link
Member

steveoh commented Nov 4, 2024

Richard Saathoff has brought to our attention that the deq tank risk tool relies on this data which is no longer available in the open sgid. He's going to run with the mature support data in agol for this months report.

steveoh added a commit to agrc/DEQ-TankRisk that referenced this issue Nov 6, 2024
@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@steveoh steveoh added the waiting Need another entity to act label Nov 12, 2024
@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@stdavis stdavis removed the waiting Need another entity to act label Dec 9, 2024
@ZachBeck
Copy link
Member

@stdavis does this layer need to be shelved or removed entirely?

@stdavis
Copy link
Member Author

stdavis commented Dec 11, 2024

does this layer need to be shelved or removed entirely?

It's up to the data team. I don't have any preference. I don't know anything more about it other than what I've put in this issue.

@ZachBeck
Copy link
Member

Ok, I'll remove it and keep it consistent with the other layers in this set of porter issues.

@agrc-conductor

This comment was marked as outdated.

@agrc-conductor

This comment was marked as outdated.

@stdavis
Copy link
Member Author

stdavis commented Dec 16, 2024

@ZachBeck It looks like you mark the task to assign data team tasks as complete but there are a few that seem like data team tasks without names on them. Are you expecting those to be done by our team?

@ZachBeck
Copy link
Member

No, just getting sloppy in my old age. I'll take care of them.

@agrc-conductor
Copy link

conductor results for tasks - 356

check status
stdavis has completed 12 out of 12 tasks 👍
ZachBeck has completed 5 out of 5 tasks 👍
steveoh has completed 4 out of 4 tasks 👍
jacobdadams has completed 1 out of 1 tasks 👍
gregbunce has completed 1 out of 1 tasks 👍
rkelson has completed 1 out of 1 tasks 👍

@agrc-conductor
Copy link

conductor results for environment.DWQAssessmentUnits

check status
internal sgid 👍
meta table 👍
stewardship
- porter issue link 👍

@stdavis stdavis closed this as completed Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deprecation Removing data and or a service porter issue related to adding and removing data and services
Projects
None yet
Development

No branches or pull requests

4 participants