Establish a pathway/workflow from collaboration data (Portal) to production (UTRANS/SGID) database

[gregbunce]

Benefit

There's great benefit in collaborating with our stewards and users, however, under this workflow, we need a pathway (as we transition away from UTRANS) for these edits back to the projection database (SGID)

Acceptance Criteria

• An established workflow for trails in which the collaboration edits in the Portal DB (from WFRC, etc) find their way back to SGID (open data, and open data)

Notes

Over time, this workflow may change especially once we deprecate UTRANS. For now, UTRANS needs to be in the mix, until we migrate the existing ArcMap tools/processes to Pro.

No response

Risks

No response

Issue Reference

refs #

[steveoh]

A modified farm from agol path could work here.

[gregbunce]

not a ton of progress was made on this feature in terms of roads data this quarter. i was able to establish a path forward for the trails data in Portal, and migrate that layer out of UTRANS however we are on hold until we work out the distributed collaboration synchronization issue that we are having with Portal. we are putting a ticket in with esri to resolve this. once this is worked out, we can move the trails data to Portal/Enterprise.
the roads are another story. that will take more time to Portal. that will hinge on the what we discover in in issue 286 (we'll be moving that issue to a new quarter)

[gregbunce]

once we get a handle on the work that needs to be done that's outlined in #286 we'll be able to revisit this for the roads data.