-
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 HEALTH.HealthCareFacilities from SGID #256
Comments
conductor results for tasks - 256
|
4 similar comments
conductor results for tasks - 256
|
conductor results for tasks - 256
|
conductor results for tasks - 256
|
conductor results for tasks - 256
|
conductor results for tasks - 256
|
adding blocked since work hasn't started |
Waiting on updated facilities from Health. |
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 HEALTH.HealthCareFacilities
|
conductor results for tasks - 256
|
conductor results for HEALTH.HealthCareFacilities
|
conductor results for tasks - 256
|
Do folks think this will need a new retention schedule as it moves to "Shelved"? it seems like it will, as it is different from non shelved. |
In my opinion it probably doesn't need to be shelved. It lived in the SGID for longer than 6 months and archives should have a copy so I believe we are covered there. The schedule it is on says archives will retain it in perpetuity, which I would suggest maybe a shorter lifespan since it doesn't appear to have historical relevance. |
conductor results for HEALTH.HealthCareFacilities
|
conductor results for tasks - 256
|
conductor results for HEALTH.HealthCareFacilities
|
conductor results for tasks - 256
|
conductor results for tasks - 256
|
conductor results for HEALTH.HealthCareFacilities
|
conductor results for tasks - 256
|
conductor results for HEALTH.HealthCareFacilities
|
Sorry to reopen the conversation. We're shelving this layer, but I'm wondering if we shouldn't just do a hard delete it and keep a copy in our google drive. It seems as though it's been completely superseded by the new layer and there's not any reason to keep the historic data around (ie, is anyone going to want to compare this with the new one to track changes over time?). |
I agree. When Matt and I were looking at the shelved category items, it appeared that there are many more shelved items than seemed to have historical relevance. Maybe I need a refresher on when items should be shelved or we need to take a closer look at the process to understand what's being added there. |
From our policy:
|
Tracking in agrc/planning-queue#452 |
conductor results for tasks - 256
|
conductor results for HEALTH.HealthCareFacilities
|
conductor results for tasks - 256
|
conductor results for HEALTH.HealthCareFacilities
|
conductor results for tasks - 256
|
conductor results for HEALTH.HealthCareFacilities
|
conductor results for tasks - 256
|
conductor results for HEALTH.HealthCareFacilities
|
conductor results for tasks - 256
|
conductor results for HEALTH.HealthCareFacilities
|
conductor results for tasks - 256
|
conductor results for HEALTH.HealthCareFacilities
|
conductor results for tasks - 256
|
conductor results for HEALTH.HealthCareFacilities
|
conductor results for tasks - 256
|
conductor results for HEALTH.HealthCareFacilities
|
conductor results for tasks - 256
|
conductor results for HEALTH.HealthCareFacilities
|
done |
Summary
HEALTH.HealthCareFacilities hasn't been updated in years. To facilitate the update process the current HealthCareFacilities needs to be deprecated and replaced by a dataset with the same name and new schema that is the same as the source data from the Dept of Health.
Migration Guide
AGOL data will be deprecated and shelved to make way for the new health care facilities
This dataset will be replaced by HEALTH.HealthCareFacilities which is named health.health_care_facilities in the Open SGID.
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:
SGID.META.AGOLItems
table (@ZachBeck , completed:2024/07/08
)2024/07/08
)2024/07/08
)2024/07/08
)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 (@ZachBeck , completed:2024/07/08
)SGID.META.AGOLItems
table. This will trigger the removal of this item in Open SGID (@ZachBeck, completed:2024/07/15
)2024/09/17
)Hard Delete
Target Date: 2024/07/23
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/23
)2024/07/22
).2024/09/17
)AGOL_ITEM_ID
field inSGID.META.AGOLItems
to something other than an Item ID and manaually changing the sharing settings (remove the item from all SGID groups, remove Public sharing),SGID.META.AGOLItems
to theAGOLItems_shelved
table in AGOL and changing theAGOL_ITEM_ID
field inSGID.META.AGOLItems
toshelved
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:2023/00/00
)2023/07/23
)- [ ] Add this porter url to theDeprecated
field of the Stewardship record (name, completed:2023/00/00
)SGID.META.AGOLItems
table (@ZachBeck, completed:2024/07/15
)AGOLItems_shelved
table if shelving (see below)AGOL_ITEM_ID
field tohosted by <agency>
for Farm from AGOLAGOL_ITEM_ID
field toexclude from AGOL
to not publish to ArcGIS Online2024/07/23
)SGID.META.ChangeDetection
(@stdavis , completed:2023/07/29
)2023/07/29
)data/hashed/changedetection.gdb/TableHashes
(@stdavis, completed:2023/07/29
)Shelve/Static
Choose one based on situation.
- [ ] Upload toUtahAGRC/AGRC_Shelved
folder in AGOL (New shelved item not already in AGOL) (name , completed:2023/00/00
)- [x] Move existing AGOL item toAGRC_Shelved
AGOL folder (shelving an item already in AGOL) (@ZachBeck, completed:2024/07/23
)- [ ] Upload to appropriateUtahAGRC/{SGID Category}
folder in AGOL (forstatic
datasets) (name, completed:2023/00/00
)Add record to table.
- [x] Add record toAGOLItems_shelved
table in ArcGIS Online withshelved
orstatic
in theCATEGORY
field (@ZachBeck, completed:2023/07/23
)🤖 Automation validation
name
with their github@name
.2020/01/01
when the task is verified.Strikeout all items that do not apply.2024/08/07
)2024/08/07
)shelved
/static
/Deprecated
information (@jacobdadams on2024/07/09
)Are there service dependencies
2023/09/17
)Notification
Group Task Assignments
The text was updated successfully, but these errors were encountered: