Closed ZachBeck closed 2 years ago
check | status |
---|---|
ZachBeck has completed 2 out of 2 tasks | :+1: |
@steveoh has completed 0 out of 4 tasks | :no_entry: |
@jacobdadams has completed 0 out of 1 tasks | :no_entry: |
@gregbunce has completed 0 out of 1 tasks | :no_entry: |
@rkelson has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
ZachBeck has completed 2 out of 2 tasks | :+1: |
@steveoh has completed 0 out of 4 tasks | :no_entry: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@gregbunce has completed 0 out of 1 tasks | :no_entry: |
@rkelson has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
ZachBeck has completed 2 out of 2 tasks | :+1: |
@steveoh has completed 0 out of 4 tasks | :no_entry: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@gregbunce has completed 0 out of 1 tasks | :no_entry: |
@rkelson has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
ZachBeck has completed 2 out of 2 tasks | :+1: |
@steveoh has completed 0 out of 4 tasks | :no_entry: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@gregbunce has completed 0 out of 1 tasks | :no_entry: |
@rkelson has completed 0 out of 1 tasks | :no_entry: |
check | status |
---|---|
ZachBeck has completed 2 out of 2 tasks | :+1: |
@steveoh has completed 0 out of 4 tasks | :no_entry: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@gregbunce has completed 0 out of 1 tasks | :no_entry: |
@rkelson has completed 0 out of 1 tasks | :no_entry: |
@ZachBeck please assign all the unassigned tasks in this issue to yourself and/or coordinate with others so we can finish this up.
In my opinion it is up to @gregbunce and I as the assigners to make sure they are all assigned.
In my opinion it is up to @gregbunce and I as the assigners to make sure they are all assigned.
Apologies @ZachBeck and @steveoh for stepping out of line.
thanks for the nudge, @nathankota! @ZachBeck are you doing a soft delete first (see the options above)? Feel free to assign most of the tasks to yourself, or others if needed. I'm happy to do the assigning as well as long as you let me know if it's a soft delete first?
Zach is out today and this has been a weird porter issue because he replaced the existing dataset in our internal SGID. All our normal checks don't really work because all the names are the same. I don't believe the soil layer was ever pushed out to the other SGID facets? So what is being deprecated is only an arcgis online item. This very well may be done but I'm unsure on all the details and if I'm telling lies or not.
check | status |
---|---|
ZachBeck has completed 2 out of 2 tasks | :+1: |
@steveoh has completed 0 out of 4 tasks | :no_entry: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@gregbunce has completed 0 out of 1 tasks | :no_entry: |
rkelson has completed 1 out of 1 tasks | :+1: |
Shouldn't the person who creates the issue do the assigning? Steve is mostly right... the old soils data was replaced with a new version with a different schema and the agol item needed to be deprecated and shelved (which has been done). The new and improved soils data is in internal-sgid and open-sgid as well as agol and open data. I'll try to get this cleaned up a little but it's pretty much ready to be closed. Sorry for the confusion.
Shouldn't the person who creates the issue do the assigning?
We've been operating that the Group Task Assignments
are done by the 3 people in the list there to keep it consistent. I think it's great if the person creating the ticket assigns themselves to tasks. But we created the group task assignments to divvy them up to the right people when the issue creator may not know who or what to do.
check | status |
---|---|
ZachBeck has completed 2 out of 2 tasks | :+1: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@gregbunce has completed 0 out of 1 tasks | :no_entry: |
@steveoh has completed 0 out of 1 tasks | :no_entry: |
rkelson has completed 1 out of 1 tasks | :+1: |
check | status |
---|---|
ZachBeck has completed 2 out of 2 tasks | :+1: |
jacobdadams has completed 1 out of 1 tasks | :+1: |
@gregbunce has completed 0 out of 1 tasks | :no_entry: |
@steveoh has completed 0 out of 1 tasks | :no_entry: |
rkelson has completed 1 out of 1 tasks | :+1: |
Summary
Old, static Utah Soils agol service needs to be renamed and shelved to make way for new soils data with an updated schema that will receive yearly updates.
Migration Guide
AGOL data will be renamed and shelved, users should repoint connections to new soils data at earliest convenience.
This dataset will be replaced by new NRCS soils which will be named Soils in the Open SGID and Utah Soils 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
.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:
~- [ ] Prepend "(Mature Support)" to the end of the item title (name, completed:
2022/00/00
)~ ~- [ ] Remove all tags other than "Deprecated" (name, completed:2022/00/00
)~ ~- [ ] Add note to ArcGIS Online description and default popup noting when layer will be deleted and any replacement layer (name, completed:2022/00/00
)~ ~- [ ] Unshare item from Open Data (name, completed:2022/00/00
)~ ~- [ ] Update the SGID Index row as deprecated by pasting the related Porter issue URL in the Deprecated field (name, completed:2022/00/00
)~ ~- [ ] Mark ArcGIS Online item as deprecated in preparation for future deletion (name, completed:2022/00/00
)~ ~ - [ ] ChangeAuthoritative
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 (name, completed:2022/00/00
)~ ~ - [ ] After one successful run of Auditor, remove the row from theSGID.META.AGOLItems
table. This will trigger the removal of this item in Open SGID (name, 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.
~- [ ] Manually remove data from the Internal SGID (name, completed:
2022/00/00
)~2022/00/00
)~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.2022/00/00
)~ ~- [ ] Update relevant gis.utah.gov data pages (name, completed:2022/00/00
)~ ~- [ ] Add this porter url to theDeprecated
field of the Stewardship record (name, completed:2022/00/00
)~ ~- [ ] UpdateSGID.META.AGOLItems
table (name, completed:2022/00/00
)~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 Online ~- [ ] Delete Google Drive data (name, completed:2022/00/00
)~ ~- [ ] Remove row fromSGID.META.ChangeDetection
(name, completed:2022/00/00
)~ ~- [ ] Remove data from forklift hashing and receiving (name, completed:2022/00/00
)~ ~- [ ] Remove row fromdata/hashed/changedetection.gdb/TableHashes
(name, completed:2022/00/00
)~Shelve/Static
Choose one based on situation.
AGRC_Shelved
AGOL folder (shelving an item already in AGOL) (@ZachBeck , completed:2022/04/28
) ~- [ ] - [ ] Upload toUtahAGRC/AGRC_Shelved
folder in AGOL (New shelved item not already in AGOL) (name , completed:2022/00/00
)~ ~- [ ] Upload to appropriateUtahAGRC/{SGID Category}
folder in AGOL (forstatic
datasets) (name, completed:2022/00/00
)~Add record to table.
AGOLItems_shelved
table in ArcGIS Online withshelved
orstatic
in theCATEGORY
field (@ZachBeck , completed:2022/04/28
):robot: Automation validation
name
with their github@name
.2020/01/01
when the task is verified.~- [ ] Remove data from Open SGID (@steveoh on
2022/00/00
)~ ~- [ ] sgid-index (@steveoh on2022/00/00
)~shelved
/static
/Deprecated
information (@jacobdadams on2022/05/03
)Are there service dependencies
Notification
~- [ ] Twitter (@steveoh)~
Group Task Assignments