Latest Contributions by PeterKnoop

It would be helpful to have some way to easily see what changes have been made in a draft story, as compared to the published version. Particularly in cases where a series of edits over time are required, before you publish the updated story. One could view the draft and published versions of a story side-by-side in two browser tabs, however, it is easy to overlook differences that way, especially if they are minor changes. Something like a compare or diff tool that would visually highlight the differences is desired. It would help one to identify blocks that had been added, deleted, or edited since the story was last published. Use cases: A group collaboratively authoring a StoryMap. They currently have to use a Shared Update group to achieve this goal, and ensure they have a way to coordinate who is authoring the story when, so that they don't run the risk of overwriting each other's edits. When it is one of the collaborators turns to edit the story, they may have forgotten what changes they have already made, and want to see what those are. Or, they may want to see what other changes have been made by other collaborators in other parts of the story since it was last published. If you are sporadically working on updating a story, or are juggling a lot of other tasks in ArcGIS, it can be difficult to remember where you left off editing story. In which case it would be helpful to remind yourself of what changes you have already made, which haven't been published yet. When an administrator is helping someone troubleshoot issues with their StoryMap, it can be helpful to identify what changes exist in the draft versus published versions, potentially narrowing down the source of a problem. ... View more

In our ArcGIS Online organization most people need to work collaboratively with others in the system, hence, we need all of our users to be able to create Shared Update groups from the start. Please make it possible to assign the privilege of "Create with update capabilities" to a custom role, so that we can grant it to our users through New member defaults. Currently, if that privilege is assigned to a custom role, then you are unable to select that role for use with New member defaults. Manually re-assigning users to a custom role with that privilege, after their account is created, is not a scalable task for our administrators. (There are scripting workarounds, however, that is not a feasible solution for all organizations.) [This Idea originates from comments on Make ‘create group with update capabilities’ a non-admin privilege, and I am posting it as its own Idea for increased, clearer awareness @JeffShaw @AmyWork3 @ReinaCMurray @PatIampietro @ColeWhite]   ... View more

Currently people viewing the Item details for a hosted item see a Size and an Attachments size. To determine the amount of Feature Storage the item uses, they have to subtract the Attachments size from the Size. As Feature Storage consumption is typically a significant expense for an ArcGIS Online organization, users need better insight into their use of Feature Storage, in order to be good stewards of their organization's resources.  This Idea proposes eliminating the need to do math to determine an item's Feature size. One could add a Feature size entry to the Item details page; or, replace Size with Feature size. It would be even more helpful if Feature Size was a column in the Content view, which would be sortable, to assist users with evaluating their hosted items consuming the most Feature Storage. ... View more

One of the challenges to fostering good data stewardship practices in ArcGIS Online -- in Higher-Education organizations in particular -- is the lack of insight users have into their own Feature Storage use. As a workaround, one can provide users with a Dashboard for monitoring their use of Feature Storage: Building such a Dashboard as an ArcGIS Online administrator, and the workflow that supports it, is described in the StoryMap: Empowered Data Stewardship: Enable users to monitor their Feature Storage use.   ... View more

Please update the StoryMap documentation that covers the "Allow duplication" setting and "Duplicate story" feature to explicitly note the latter is not supported with Public ArcGIS Online accounts. For example, on the documentation page Publish a story or briefing, in the section discussing the "Allow duplication" setting, please add a note indicating that duplication of a story by a Public Account user is not supported. It currently states, "Use the Allow duplication check box to provide ArcGIS users with access to the story to duplicate the item", however, that is not true for Public accounts, which can access the story, but are unable to duplicate it. ... View more