Latest Contributions by PeterKnoop

I don't know of a way to do this in the StoryMaps app itself. So far the best way I've found to do this requires modifying the JSON of the StoryMap using something like the ArcGIS Assistant. Below are the steps we share with our users, if they are willing to take on the risk of working directly with a story's JSON. Not required, however, if you're not comfortable working with JSON, then I would recommend making duplicates of your Briefing and StoryMap. Follow the remaining steps below using those copies until you are comfortable. Edit your destination StoryMap and add an Express Map block as a placeholder. It is not required, however, I would recommend publishing your StoryMap at this point, so that you can work on the draft version, and revert to this published version if something goes wrong. In ArcGIS Assistant, go to your Briefing and View Item JSON. Switch to the Data tab, from the default Description tab. In the "nodes" section, identify the node that contains the Express Map in your Briefing that you want to copy, and note it's id (e.g, "n-f9qxjg".) Look for that node's id in the "resources" section (near the bottom of the JSON), and note the listed itemId (e.g., "expressmap_1711645656520.json".) Now switch to the Resources tab at the top. Identify the resource(s) that represent your Express Map block in your Briefing. There should be one json resource whose name begins with draft_expressmap, which represents the current version of your Express Map in the draft version of your Briefing. If you have published your Briefing, then there should be a second resource with the same id, but whose name begins with pub_expressmap. If you you have no unpublished changes in your Briefing, then the two are the same. Otherwise, decide which version of you Express Map you want to copy to your StoryMap, the draft or published version. Click on the name of the Express Map json file that you want to copy (either draft or published), and copy the entire content of the file. (If needed, save it somewhere temporarily, as there a number of steps before you need to paste it.) Now go to your StoryMap in ArcGIS Assistant and View Item JSON. Switch to the Data tab. In the "nodes" section, identify the placeholder Express Map block that you added, and note its id. Look for that node's id in the "resources" section, and note the listed itemId. Now switch to the Resources tab. Identify the resources that represent your placeholder Express Map in your StoryMap. As before, there should be two resources, a draft_expressmap and a pub_expressmap, assuming you followed the advice above and published your StoryMap. Click on the name of the draft_expressmap to open the JSON view of it. Click on the "Edit resources" button in the top-right to enable editing the JSON content. Replace all of the JSON with what you copied from the Briefing resource item, and hit "Save." (I would recommend replacing only the draft version at this time, then viewing your StoryMap in edit mode, and only then publishing your StoryMap if you happy with what you have done. If something has gone wrong, then you can discard unpublished changes to revert to your original version of the StoryMap.) Now open your StoryMap in edit mode and you should see the Express Map you copied from your Briefing has replaced your empty placeholder Express Map.  ... View more

As @ChristopherCounsell notes, what you are looking for is a group's capabilities. If you set the parameter users_update_items=True when you create a group, then 'updateitemcontrol' is added to the group's capabilities. There are other capabilities a group can have, such as "distributed", so you should not rely solely on testing that capabilities is not null. I would recommend explicitly testing that 'updateitemcontrol' is in the group's list of capabilities.  You can specify a capability as part of your group search query, so one way to retrieve a list of shared update groups is: shared_udpate_groups = gis.groups.search( # A shared update group has 'updateitemcontrol' as one of its capabilites. query = 'capabilities:updateitemcontrol', # 10,000 appears to be a hard limit. # If more than 10,000 might be returned, then split up your query and aggregate the results. max_groups = 10000 )   ... View more