-
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 EMS Facilities from SGID #297
Labels
deprecation
Removing data and or a service
porter
issue related to adding and removing data and services
Comments
jacobdadams
added
deprecation
Removing data and or a service
porter
issue related to adding and removing data and services
labels
Mar 4, 2024
When does the brown out date start and when should the final deletion date be? |
conductor results for tasks - 297
|
conductor results for tasks - 297
|
2 similar comments
conductor results for tasks - 297
|
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
19 tasks
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
Ok, the layer has been deleted from Internal and AGOL. There was no gis.utah.gov content for it. If I've done everything right, it should soon be completely gone from everything (except a backup zip in google drive). |
conductor results for tasks - 297
|
conductor results for HEALTH.EMSFacilities
|
This looks ready to be closed 🏁 |
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
Summary
As near as I can tell, based on the blog post "Utah SGID Layer Updates" dated 2013-06-05, the EMS Facilities layer was supposed to be removed in favor of a new Emergency Medical Services layer. However, despite a corresponding "Removal" entry in the data stewardship log, they both appear to have continued in the SGID and have both made it into AGOL.
Our hub/open data site includes both, and the current data page points to the older one.
I propose completely expunging the older layer and using the website update process to update the data page.
Brownout:
21 June 2024
Removal:
8 July 2024
Migration Guide
Repoint data to the Emergency Medical Services Layer.
This dataset has been replaced by Emergency Medical Services which is named
health.emergency_medical_services
in the Open SGID andutah-emergency-medical-services
in ArcGIS Online Hub (Open Data) .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:
SGID.META.AGOLItems
table (@jacobdadams, completed:2024/06/21
)2024/06/21
)2024/06/21
)2024/06/21
)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 (@jacobdadams, completed:2024/06/21
)SGID.META.AGOLItems
table. This will trigger the removal of this item in Open SGID (@jacobdadams, completed:2024/06/25
)2024/00/00
)2024/06/25
).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.
2024/07/08
)2024/00/00
).2024/07/08
)- [ ] Remove Farm from AGOL connection (name, completed:2024/00/00
)2024/07/08
)Deprecated
field of the Stewardship record (@jacobdadams, completed:2024/06/21
)SGID.META.AGOLItems
table (@jacobdadams, completed:2024/07/08
)- 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 Online- [ ] Delete Google Drive data (name, completed:2024/00/00
)SGID.META.ChangeDetection
(@stdavis, completed:2024/07/08
)2024/07/08
)data/hashed/changedetection.gdb/TableHashes
(@stdavis, completed:2024/07/08
)🤖 Automation validation
name
with their github@name
.2020/01/01
when the task is verified.Strikeout all items that do not apply.2024/07/15
)2024/07/15
)Deprecated
information (@jacobdadams on2024/06/24
)Are there service dependencies
2024/03/11
)Notification
Group Task Assignments
The text was updated successfully, but these errors were encountered: