Remove OGM Items from AGRC AGOL Org

[stdavis]

Summary

DOGM has hosts their own AGOL items for these datasets now so we should not duplicate their offerings. The data will continue to be hosted in SGID, SGID10 and OpenSGID.

AGRC Items

• Utah Oil Gas Wells
• Utah Oil Gas Wells Paths
• Utah Oil Gas Wells Down Holes

DOGM Items

• Oil and Gas Well Locations
• Oil and Gas Wells Paths
• Oil and Gas Well Bottom Hole Locations

Triage

• Data Team Triage
• Dev Team Triage (@stdavis)
• Cadastre Team Triage

Remove data from the following areas

• ArcGIS Online (@gregbunce)
  • update description to point to DOGM items (@stdavis)
  • Mark as deprecated (@stdavis)
  • Unshare AGRC items (@nathankota)
• Google Drive (@ZachBeck )
• Open data (@nathankota )
  • How do we switch our open data from our items to DOGMs? Do we need to ask them to share them with us? SITLA land ownership would be a good example.
• Backseat driver (@stdavis)

Copy data to the following areas

deleting

• [ ] Upload to UtahAGRC/AGRC_Shelved folder in AGOL (assigned to)
• [ ] Move existing AGOL item to AGRC_Shelved AGOL folder (assigned to)
• [ ] Upload to appropriate UtahAGRC/{SGID Category} folder in AGOL (for "static" datasets) (assigned to)

Update information in the following areas

• gis.utah.gov data pages (@steveoh )
• Stewardship doc and sgid-index (@steveoh)
• Update row from SGID.META.AGOLItems (@stdavis)

Is there a forklift pallet?

• Update OGMPallet to point to DOGM AGOL services (@stdavis)
• [ ] Remove row from data/hashed/changedetection.gdb/TableHashes (@stdavis)

Notification

- [ ] Blog post (assigned to)

• Twitter (@steveoh)
  • Intent
  • Completed

[jacobdadams]

Not outside of the Auditor source, no. Where would be the best place to document that? Do we have a general readme for the metatable? If not, would that be worth creating?

[steveoh]

Would the metadata for the table in SDE be a reasonable place or do we want more simple access?

[jacobdadams]

That seems like a sensible place.

I also wonder if it wouldn't be beneficial to have a centralized collection of docs somewhere for all the different processes — kind of translating the Porter templates to step-by-step instructions. This collection could also include some reference docs, like a description of the metatable and its fields.

[steveoh]

I am ok with that. Do you want to create a metatable github repo or something? We can also take this to slack to keep this issue on topic.

[steveoh]

/remind us to delete the services on 9/21

[reminders]

@steveoh set a reminder for Sep 21st 2020

[steveoh]

blocked by open data sharing

gis website

• keep drive links until open data is available
• replace existing agol links to updated services

[nathankota]

AGOL user OGMGIS_utahDNR has been added to the AGRC Energy group. OGM will utilize the presentation and minimum metadata recommendations then share the items.

[nathankota]

OGM has shared the following items to the Energy group:

• Oil and Gas Well Locations
• Oil and Gas Wells Paths
• Oil and Gas Well Bottom Hole Locations

[steveoh]

How much do we want to try to work with them to improve their items by using our conventions?

For example...

1. Updating the title from Oil and Gas Well Locations -> Utah Oil and Gas Well Locations
2. The layer name is less than ideal 🏄🏼
   
3. The tags are all duplicates of the title and of themself and the credits are empty.
   

[nathankota]

How much do we want to try to work with them to improve their items by using our conventions?

They seem willing to improve their data offerings. I will follow-up.

[stdavis]

Those changes would likely break their forklift pallet and will require updates to get it going again. Not a huge deal but it will take some work.

[stdavis]

I updated the AGRC AGOL Item summaries to point to the DOGM Items. I also updated the AGOLItems table for these rows.

[steveoh]

So our oil and gas page has the wells, fields, and some unit thing. Only one of the deprecated links was referenced and the fields still points to one of our agol services. What should we suggest to do with that page and the agol item they didn't replace?

Also the oil and gas well locations open data item does not have the FGDB download checkbox checked.

[stdavis]

Also the oil and gas well locations open data item does not have the FGDB download checkbox checked.

I believe that @nathankota was working with Michael at DOGM to get this turned on.

What should we suggest to do with that page and the agol item they didn't replace?

I would suggest that we update the deprecated links and then leave the other items as-is for now.

[stdavis]

Are we sure that we want to delete these services? Wells is still getting a lot of traffic:

[stdavis]

I'd suggest that we at the very least unshare them and let them sit for another few weeks before deleting them. Then we have the option of switching them back on if there is a major issue that someone needs to fix.

[steveoh]

Ok so the remaining items are

• [ ] unshare AGOL items
• [ ] create a reminder to hard delete them
• update back seat driver

[steveoh]

remaining items

• reach out to see if DOGM is using the data.
• select date 2 weeks after unshare to delete

[stdavis]

I've removed the data from backseat driver.

[nathankota]

OGM is okay with the unshare-then-delete strategy for the AGRC data.

[steveoh]

ok so are we unsharing today then? Was OGM using the agrc services?

[nathankota]

Sharing has been changed to Organization only and removed from the Energy group for the following AGRC Items

• Utah Oil Gas Wells
• Utah Oil Gas Wells Paths
• Utah Oil Gas Wells Down Holes

[nathankota]

/remind to delete on October 13. @gregbunce it sounds like you save deletions in G-Drive prior to their demise?

[reminders]

@nathankota set a reminder for Oct 13th 2020

[gregbunce]

the three agrc agol items listed above have been deleted from agol and are backed up along with their service definition files to the google drive (AGRC Projects/SGID/deprecated layers)

[gregbunce]

from my perspective, this issue can be closed.