At this years GeoConX conference we held a technical session on administering your portal. Following the session numerous attendees asked for access to some of the tools we highlighted, so I wanted to recap the session and share all of those with you. My team at Esri administers our demonstration environments for our global business development team, which includes 2000+ users. We maintain a hybrid ArcGIS Enterprise and Online environment, and below are the ways, we internally at Esri, have outlined our governance practices.
Authoritative Content - authoritative content is all about separating the 'portal clutter' or sandbox content from the authoritative web maps, apps, and layers that are shared with users in the portal, and the best practices around doing so. Here are some useful tools and best practices for maintaining authoritative content:
Organization & Accessibility - A clean and organized portal is a happy portal. Users will continue to come back to the portal if it is well organized, content can be found relatively easy, and content is easily accessible. Here are some useful tools and best practices for maintaining organization & accessibility:
Availability - With more and more organizations and employees adopting the notion of 'work' being a state of mind and not a location, the need to have business applications running 24/7 is crucial. Here are some useful tools and best practices for ensuring high availability of your portal and apps:
Management - Governance and management of the portal is key to keeping the portal sustainable and ensuring all the key elements above. Here are some useful tools and best practices for management of your portal:
During the development stage of apps, contents will be kept in the curator’s user contents. The app(s) may be shared with the Sandbox group for testing and feedback from other users. Once a working prototype of the item is complete, the item may be shared with the Prototyping group.
During the prototyping stage, the app is kept in the Prototyping group while the content is tested by additional developers. If changes are made to the app during this stage, the content will need to be removed from the Prototyping group and shared back into the Sandbox group. When the prototype has been tested and is working, the app may be shared with the Staging group for preparation of final release.
During the staging stage, all associated contents (maps, layers, apps) for the app must be shared into the Staging group. At that point, a proper thumbnail, summary, and description should be added to the app and associated contents. The curator or developer of the contents will then document that app. The GIS admin of the portal will then QAQC the contents and the documentation. When the app is finalized, the admin will share the app into the proper business function group, and move all associated contents (web map and layers) from the curator’s user contents into the admin’s user contents, this reduces the possibility of content associated with the app accidentally being deleted or modified.
Once the app is released and in production, the admin will host and keep the contents for the app in their contents.
As always, feel free to reach out with any feedback or questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.