search

agrc / porter

UGRC tracks the additions, replacements, and deletions of SGID items (in the broadest sense of add, replace, or delete) through issues in this repository.
https://gis.utah.gov/documentation/policy/
MIT License
2 stars 0 forks source link

Remove and shelve outdated Utah US Congress Districts from Open SGID (remain in AGOL as shelved) #217

Closed gregbunce closed 1 year ago

gregbunce commented 1 year ago

Summary

A short summary of the situation. These two Congress Districts are no longer active. As of Jan 2023, we are now using the latest US Congresseation districts and these need to be removed from Open Data but made available in AGOL under the 'shelved' tag. Also, we should rename the item names in AGOL to be more descriptive and to better match our current naming convention for this layer. The remaining should be as follows:

Migration Guide

This dataset has been replaced by Utah US Congress Districts 2022 to 2032.

At this point, we should be migrating applications and users away from this outdated layer and onto the latest data.

Let's do a soft delete before we do a hard delete (aka: remove from Open Data) because of the many systems and users that were/are potentially using this data.

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:

Shelve/Static

Choose one based on situation.

Add record to table.

Hard Delete (to happen after 2/15/2023)

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.

:robot: 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.
agrc-conductor commented 1 year ago

conductor results for tasks - 217

check status
@gregbunce has completed 0 out of 14 tasks :no_entry:
@gregbunceon has completed 0 out of 1 tasks :no_entry:
@steveoh has completed 0 out of 3 tasks :no_entry:
@jacobdadams has completed 0 out of 1 tasks :no_entry:
@rkelson has completed 0 out of 1 tasks :no_entry:
agrc-conductor commented 1 year ago

conductor results for tasks - 217

check status
@gregbunce has completed 0 out of 14 tasks :no_entry:
@gregbunceon has completed 0 out of 1 tasks :no_entry:
@steveoh has completed 0 out of 3 tasks :no_entry:
@jacobdadams has completed 0 out of 1 tasks :no_entry:
@rkelson has completed 0 out of 1 tasks :no_entry:
gregbunce commented 1 year ago

/remind me to finish and close out this issue on 2/15/2023

github-actions[bot] commented 1 year ago

@gregbunce set a reminder for 2/15/2023

github-actions[bot] commented 1 year ago

:wave: @gregbunce, finish and close out this issue

agrc-conductor commented 1 year ago

conductor results for tasks - 217

check status
gregbunce has completed 15 out of 15 tasks :+1:
@steveoh has completed 0 out of 6 tasks :no_entry:
@jacobdadams has completed 0 out of 1 tasks :no_entry:
@nathankota has completed 0 out of 1 tasks :no_entry:
@rkelson has completed 0 out of 1 tasks :no_entry:
agrc-conductor commented 1 year ago

conductor results for tasks - 217

check status
gregbunce has completed 15 out of 15 tasks :+1:
@steveoh has completed 0 out of 6 tasks :no_entry:
@jacobdadams has completed 0 out of 1 tasks :no_entry:
@nathankota has completed 0 out of 1 tasks :no_entry:
@rkelson has completed 0 out of 1 tasks :no_entry:
steveoh commented 1 year ago

My validation tasks look good.

agrc-conductor commented 1 year ago

conductor results for tasks - 217

check status
gregbunce has completed 15 out of 15 tasks :+1:
steveoh has completed 6 out of 6 tasks :+1:
jacobdadams has completed 1 out of 1 tasks :+1:
@nathankota has completed 0 out of 1 tasks :no_entry:
@rkelson has completed 0 out of 1 tasks :no_entry:
agrc-conductor commented 1 year ago

conductor results for POLITICAL.USCongressDistricts2002

check status
internal sgid :+1:
meta table :+1:
stewardship
- deprecation issue link :no_entry:
steveoh commented 1 year ago

Shouldn't there be a stewardship deprecation link and checkbox in this issue?

@gregbunce should we wait for @nathankota's thing before closing this?

gregbunce commented 1 year ago

regarding the description link: yeah, i wasn't sure about that. I am fuzzy on whether we 'shelved' and 'depreciated' them or just shelved them. what do you think?

gregbunce commented 1 year ago

I think we can close it, unless i need to add deprecation links to the spreadsheet.

at this point, the data has only one endpoint and it's stable.

steveoh commented 1 year ago

If there is no deprecation link it shows up in the SGID index? I think we decided to remove shelved but not static from the index?

gregbunce commented 1 year ago

good point. yeah, the policy states, "Shelved datasets are not included in the SGID Open Data site."

I added the link. thanks for clarifying.

gregbunce commented 1 year ago

i'd say we can close this. any objections?

stdavis commented 1 year ago

I think that we should leave at least one issue open with the http://elections.utah.gov/map/district-maps task.

steveoh commented 1 year ago

That would be #223 then right?