-
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 uniquehousesenate2002 from SGID #225
Comments
conductor results for tasks - 225
|
conductor results for POLITICAL.uniquehousesenate2002
|
conductor results for tasks - 225
|
conductor results for POLITICAL.uniquehousesenate2002
|
note: I have this on my radar to begin looking at later in the week. |
🔔🔔🔔 |
conductor results for tasks - 225
|
conductor results for POLITICAL.uniquehousesenate2002
|
conductor results for tasks - 225
|
conductor results for POLITICAL.uniquehousesenate2002
|
conductor results for tasks - 225
|
conductor results for POLITICAL.uniquehousesenate2002
|
conductor results for tasks - 225
|
conductor results for POLITICAL.uniquehousesenate2002
|
conductor results for tasks - 225
|
conductor results for POLITICAL.uniquehousesenate2002
|
conductor results for tasks - 225
|
conductor results for POLITICAL.uniquehousesenate2002
|
conductor results for tasks - 225
|
conductor results for POLITICAL.uniquehousesenate2002
|
conductor results for tasks - 225
|
conductor results for POLITICAL.uniquehousesenate2002
|
conductor results for tasks - 225
|
conductor results for POLITICAL.uniquehousesenate2002
|
Looks like everything has been checked off the list. If you agree, @DenisePeterson would you like to do the honors of closing this issue? |
It looks like there's not an entry for this item in the AGOLItems_shelved table, so Auditor doesn't know it should be shelved. @DenisePeterson, do you want to add the relevant row in that table and then let me know? I can then run auditor on it and make sure it gets moved appropriately. And again, this was caused by the auditor verification actually needing to happen twice: once for the deprecation in the soft delete stage and again for the shelving during the hard delete. |
Please update the dates when you complete the tasks @DenisePeterson so we can keep track of everything |
fixed the table issue to shelve uniquehousesenate2002 and close. |
let's verify auditor and close this out when it's complete. @DenisePeterson if you could update all the dates next to your tasks as well that would be great! |
We did both, and I added a second checkbox for it under the validation checks. |
Summary
The layers that went into creating this I assume were shelved with #221 and #220
Migration Guide
The migration would be to use more current data. We have a combined 2022-2032 but I am unsure how that is different than unique house and senate.
This dataset has been replaced by () which is named () in the Open SGID and () 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/29
)2022/00/00
)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 (@DenisePeterson, completed:2023/11/29
)SGID.META.AGOLItems
table. This will trigger the removal of this item in Open SGID (@DenisePeterson, completed:2022/00/00
)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/18`)SGID.META.AGOLItems
to theAGOLItems_shelved
table in AGOL and changing theAGOL_ITEM_ID
field inSGID.META.AGOLItems
toshelved
or some other note.2022/00/00
)Deprecated
field of the Stewardship record (@DenisePeterson, completed:2023/11/29
)SGID.META.ChangeDetection
(@steveoh, completed:2023/12/11
)2023/12/11
)data/hashed/changedetection.gdb/TableHashes
(@steveoh, completed:2023/12/11
)2022/00/00
)- [ ] Delete Google Drive data (@DenisePeterson, completed:2022/00/00
)- [ ] UpdateSGID.META.AGOLItems
table (@DenisePeterson, completed:2022/00/00
)- cut and paste row toAGOLItems_shelved
table if shelving (see below)- set theAGOL_ITEM_ID
field tohosted by <agency>
for Farm from AGOL- set theAGOL_ITEM_ID
field toexclude from AGOL
to not publish to ArcGIS OnlineShelve/Static
Choose one based on situation.
AGRC_Shelved
AGOL folder (shelving an item already in AGOL) (@DenisePeterson, completed:2022/00/00
)- [ ] Upload to appropriateUtahAGRC/{SGID Category}
folder in AGOL (forstatic
datasets) (@DenisePeterson, completed:2022/00/00
)- [ ] Upload toUtahAGRC/AGRC_Shelved
folder in AGOL (New shelved item not already in AGOL) (@DenisePeterson, completed:2022/00/00
)Add record to table.
AGOLItems_shelved
table in ArcGIS Online withshelved
orstatic
in theCATEGORY
field (@DenisePeterson, completed:2022/00/00
)🤖 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
)Deprecated
information (@jacobdadams on2023/11/30
)shelved
information (@jacobdadams on2023/12/18
)Are there service dependencies
2023/03/13
)Notification
Group Task Assignments
The text was updated successfully, but these errors were encountered: