Closed stdavis closed 3 years ago
check | status |
---|---|
@stdavis has completed 2 out of 3 tasks | :no_entry: |
@steveoh has completed 1 out of 2 tasks | :no_entry: |
@gregbunce has completed 0 out of 1 tasks | :no_entry: |
@rkelson has completed 0 out of 1 tasks | :no_entry: |
Auditor has labeled this deprecated as of this morning.
check | status |
---|---|
@gregbunce has completed 7 out of 8 tasks | :no_entry: |
stdavis has completed 3 out of 3 tasks | :+1: |
@steveoh has completed 1 out of 2 tasks | :no_entry: |
@rkelson has completed 0 out of 1 tasks | :no_entry: |
this data is scheduled to be deleted from agol on 5/10/2021
From what I can tell, this issue can now be closed. Can someone double-check me on that? A few thumbs up and I'll click the button (or feel free to do the honors).
The website needs updating on https://gis.utah.gov/data/utilities/retail-culinary-water-suppliers/ and I don't see it in the sgid index which means it's missing a record.
This should not have been marked as deprecated in the stewardship sheet since it was a replacement.
check | status |
---|---|
gregbunce has completed 8 out of 8 tasks | :+1: |
stdavis has completed 3 out of 3 tasks | :+1: |
steveoh has completed 2 out of 2 tasks | :+1: |
rkelson has completed 1 out of 1 tasks | :+1: |
I think that we screwed this deprecation up a little bit. I shouldn't have included this task:
That removed the table from open sgid. I found out today because DEQ is attempting to query that table via our web API. I've added the row back into the meta table.
I also noticed that there is a version of this data in SGID called SGID.UTILITIES.RetailCulinaryWaterServiceAreas
. Should that have been removed? I've verified that forklift is updating SGID.UTILITIES.CulinaryWaterServiceAreas
. Can we just trash SGID.UTILITIES.RetailCulinaryWaterServiceAreas
or should we open a new porter issue?
@ZachBeck Was able to delete SGID.UTILITIES.RetailCulinaryWaterServiceAreas
today so I think that everything should be wrapped up now.
/remind me tomorrow to look for culinary water service areas in the open sgid
Looks good.
Summary
Utilities.CulinaryWaterServiceAreas
(we want to keep this)A short summary of the situation.
SGID.Utilities.CulinaryWaterServiceAreas
has grown stale. Water Resources (DNR) now hosts this data in AGOL and has already shared this data with our org. I propose that we remove our duplicate AGOL item and wire up forklift to farm the data from the DNR AGOL service into internal SGID.I've compared the schemas between the DNR AGOL item and internal and the only difference is the
COLOR4
field which shows up in internal but it's been all nulls for as long as @rkelson's hair. The only other difference that I could find was that the DNR AGOL item doesn't have the field aliases that we have which don't translate to open SGID anyways.Migration Guide
A short summary of how users affected by this deprecation can modify their workflows and projects to continue to get similar or improved functionality
The migration guide is to use the DNR feature layer in arcgis online. If there was a dependency on color4 that will be a breaking change. The open sgid layer and everything else should continue to be the same except it will now be updated from the steward.
Action items
name
with their github@name
.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:
2021/04/26
)2021/04/26
)2021/04/26
)2021/04/26
)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:2021/04/26
)SGID.META.AGOLItems
table. This will trigger the removal of this item in Open SGID (@gregbunce, completed:2021/04/28
)Hard Delete
Hard deletes are final. It is recommend 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.
2021/00/00
)~2021/05/10
)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.2021/00/00
)~2021/00/00
)~Deprecated
field of the Stewardship record (name, completed:2021/00/00
)~SGID.META.AGOLItems
table (@stdavis, completed:2021/04/21
)AGOLItems_shelved
table if shelving (see below)AGOL_ITEM_ID
field tohosted by <agency>
for Farm from AGOL~AGOL_ITEM_ID
field toexclude from AGOL
to not publish to ArcGIS Online~2021/00/00
)~SGID.META.ChangeDetection
(name, completed:2021/00/00
)~2021/00/00
)~2021/04/27
)data/hashed/changedetection.gdb/TableHashes
(name, completed:2021/00/00
)~Shelve/Static
Choose one based on situation.
Not that we want to shelve this data. Probably none? @jacobdadams any thoughts?
UtahAGRC/AGRC_Shelved
folder in AGOL (New shelved item not already in AGOL) (name, completed:2021/00/00
)~AGRC_Shelved
AGOL folder (shelving an item already in AGOL) (name, completed:2021/00/00
)~UtahAGRC/{SGID Category}
folder in AGOL (forstatic
datasets) (name, completed:2021/00/00
)~Add record to table.
~- [ ] Add record to
AGOLItems_shelved
table in ArcGIS Online withshelved
orstatic
in theCATEGORY
field (name, completed:2021/00/00
)~:robot: Automation validation
name
with their github@name
.2020/01/01
when the task is verified.2021/00/00
)~2021/00/00
)~shelved
/static
/Deprecated
information (@jacobdadams on2021/00/00
)~Are there service dependencies
Other Tasks
2021/04/21
)Notification
Group Task Assignments