-
Notifications
You must be signed in to change notification settings - Fork 0
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 sgid.political.districtcombinationareas2012 from SGID #226
Comments
conductor results for tasks - 226
|
conductor results for POLITICAL.districtcombinationareas2012
|
conductor results for tasks - 226
|
conductor results for POLITICAL.districtcombinationareas2012
|
note: I have this on my radar to begin looking at later in the week. |
🔔🔔🔔 |
conductor results for tasks - 226
|
conductor results for POLITICAL.districtcombinationareas2012
|
conductor results for tasks - 226
|
conductor results for POLITICAL.districtcombinationareas2012
|
conductor results for tasks - 226
|
conductor results for POLITICAL.districtcombinationareas2012
|
conductor results for tasks - 226
|
conductor results for POLITICAL.districtcombinationareas2012
|
conductor results for tasks - 226
|
conductor results for POLITICAL.districtcombinationareas2012
|
conductor results for tasks - 226
|
conductor results for POLITICAL.districtcombinationareas2012
|
conductor results for tasks - 226
|
conductor results for POLITICAL.districtcombinationareas2012
|
conductor results for tasks - 226
|
conductor results for POLITICAL.districtcombinationareas2012
|
I believe my work is done |
Let's wait until next monday to see what conductor says. The layer doesn't show as shelved yet. I've asked jake to clarify his check and what auditor will be doing. |
Ok, the initial Auditor validation I checked off on was when auditor caught that it had been deprecated and updated the tags, title, and deprecated note. The group and folder as set to "shelved" if it's in the AGOLItems_shelved table with a CATEGORY of Thus, when we set them to deprecated in the SGID meta table, Auditor fixes the relevant bits on the item, and when the row is created in AGOLItems_shelved it actually moves it. So, for this layer, tomorrow morning's Auditor run should actually put it on the shelf where it belongs with all the other misfit toys. I'll be the first to admit this isn't a particularly elegant solution. I'd love to fix this with the asset tracker tool. |
conductor results for tasks - 226
|
conductor results for POLITICAL.districtcombinationareas2012
|
@gregbunce it looks like this is ready to be closed? |
thanks everyone. |
Summary
There is a newer version and the data that created this combination were shelved.
Migration Guide
Update to the newest data. https://gis.utah.gov/data/political/political-districts/#CombinedDistricts
This dataset has been replaced by the 2022 combined areas which is named district_combination_areas_2022 in the Open SGID and utah-district-combination-areas-2022 in the SGID Open Data.
The replaced data is still accessible via our shelved policy in AGOL (a link to the shelved item).
Action items
name
with their github@name
.Strikeout 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:
2023/11/29
)2023/11/29
)2023/11/29
)2023/11/29
)2023/11/30
)Authoritative
field tod
inSGID.META.AGOLItems
to automatically set theDeprecated
AGOL flag. Allow thed
to persist through one run of Auditor - currently, Auditor runs daily at 5:00am (@gregbunce, completed:2023/11/29
)SGID.META.AGOLItems
table. This will trigger the removal of this item in Open SGID (@DenisePeterson, completed:2023/11/30
)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.
2023/12/11
)2023/12/11
)SGID.META.AGOLItems
to theAGOLItems_shelved
table in AGOL and changing theAGOL_ITEM_ID
field inSGID.META.AGOLItems
toshelved
or some other note.2023/12/11
)Deprecated
field of the Stewardship record (@gregbunce, completed:2023/11/29
)SGID.META.AGOLItems
table (@gregbunce, completed:2023/12/11
)AGOLItems_shelved
table if shelving (see below)SGID.META.ChangeDetection
(@steveoh, completed: 2023/12/11`)data/hashed/changedetection.gdb/TableHashes
(@steveoh, completed: 2023/12/11`)2023/12/11
)- [ ] Delete Google Drive data (@gregbunce, completed:2022/00/00
)Shelve/Static
Choose one based on situation.
AGRC_Shelved
AGOL folder (shelving an item already in AGOL) (@gregbunce, completed:2023/12/11
)- [ ] Upload to appropriateUtahAGRC/{SGID Category}
folder in AGOL (forstatic
datasets) (@gregbunce, completed:2022/00/00
)- [ ] Upload toUtahAGRC/AGRC_Shelved
folder in AGOL (New shelved item not already in AGOL) (@gregbunce, completed:2022/00/00
)Add record to table.
AGOLItems_shelved
table in ArcGIS Online withshelved
orstatic
in theCATEGORY
field (@gregbunce, completed:2023/12/11
)🤖 Automation validation
name
with their github@name
.2020/01/01
when the task is verified.Strikeout all items that do not apply.2023/11/30
)shelved
/static
/Deprecated
information (@jacobdadams on2023/11/30
)Are there service dependencies
2023/03/13
)Notification
Group Task Assignments
The text was updated successfully, but these errors were encountered: