-
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 UTA Light Rail Stations from SGID #334
Labels
deprecation
Removing data and or a service
porter
issue related to adding and removing data and services
Comments
conductor results for tasks - 334
|
conductor results for Transportation.LightRailStations_UTA
|
conductor results for tasks - 334
|
conductor results for Transportation.LightRailStations_UTA
|
conductor results for tasks - 334
|
conductor results for Transportation.LightRailStations_UTA
|
20 tasks
conductor results for tasks - 334
|
conductor results for Transportation.LightRailStations_UTA
|
note about this layer and the sgid index: I used the existing row (record) for this layer in the sheet and updated the values with the newest information (name, urls, etc). |
stdavis
added a commit
to agrc/locate
that referenced
this issue
Aug 19, 2024
1 task
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
UTA now has its own ArcGIS Enterprise Portal and is hosting this layer and sharing it with UGRC's SGID (SGID on ArcGIS) via Distributed Collaboration in UGRC's AGOL.
Migration Guide
The goal is to direct our users to UTA's web service, via the SGID Index and the SGID on ArcGIS.
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 (@gregbunce, completed:2024/07/30
)2024/07/30
)2024/07/30
)2024/07/30
)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:2024/07/30
)SGID.META.AGOLItems
table. This will trigger the removal of this item in Open SGID (@gregbunce, completed:2024/08/01
)2024/07/30
)2024/08/12
).Hard Delete
Target Date: 2024/08/15
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/08/15
)2024/08/15
).2024/00/00
)2024/00/00
)2024/08/15
)downloadMetadata.ts
) (@ZachBeck, completed:2024/08/15
)SGID.META.AGOLItems
table, remove row (@ZachBeck, completed:2024/08/15
)SGID.META.ChangeDetection
(@stdavis, completed:2024/00/00
)2024/00/00
)data/hashed/changedetection.gdb/TableHashes
(@stdavis, completed:2024/00/00
)Shelve/Static
Choose one based on situation.
- [ ] Upload toUtahAGRC/AGRC_Shelved
folder in AGOL (New shelved item not already in AGOL) (name, completed:2024/00/00
)- [ ] Move existing AGOL item toAGRC_Shelved
AGOL folder (shelving an item already in AGOL) (name, completed:2024/00/00
)- [ ] Upload to appropriateUtahAGRC/{SGID Category}
folder in AGOL (forstatic
datasets) (name, completed:2024/00/00
)Add record to table.
- [ ] Add record toAGOLItems_shelved
table in ArcGIS Online withshelved
orstatic
in theCATEGORY
field (name, completed:2024/00/00
)🤖 Automation validation
name
with their github@name
.2020/01/01
when the task is verified.Strikeout all items that do not apply.2024/00/00
)2024/00/00
)shelved
/static
/Deprecated
information (@jacobdadams on2024/07/31
)Are there service dependencies
2024/08/15
)2024/08/19
)Notification
Group Task Assignments
The text was updated successfully, but these errors were encountered: