<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>idea Storymap (cascade): Multi-user edit and/or check-in/check-out mechanism in ArcGIS StoryMaps Ideas</title>
    <link>https://community.esri.com/t5/arcgis-storymaps-ideas/storymap-cascade-multi-user-edit-and-or-check-in/idi-p/923466</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A massive hit in our organisation is the storymap configured app, and in particular the cascade template then. So much so that our scrum teams post their reviews in the storymaps, and a lot of their users in marketing pretty much do the same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One issue we keep running into is user A opening a story map to edit, and user B deciding to do the same, and well... whoever saves last... determines the outcome, overwriting the poor other users' edits. Sadly they occasionally only find this out right as they are about to go on a big screen in front of a crowd...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We'd like it to be that these storymaps could be either:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Version managed with merge/roll back functionality&lt;/LI&gt;&lt;LI&gt;Multi-user edit&lt;/LI&gt;&lt;LI&gt;Prevent-overwrite (such as classic network shared MS Office files: "this is open for edit by user X, you can not save changes")&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 07 Mar 2018 08:45:35 GMT</pubDate>
    <dc:creator>Anonymous User</dc:creator>
    <dc:date>2018-03-07T08:45:35Z</dc:date>
    <item>
      <title>Storymap (cascade): Multi-user edit and/or check-in/check-out mechanism</title>
      <link>https://community.esri.com/t5/arcgis-storymaps-ideas/storymap-cascade-multi-user-edit-and-or-check-in/idi-p/923466</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A massive hit in our organisation is the storymap configured app, and in particular the cascade template then. So much so that our scrum teams post their reviews in the storymaps, and a lot of their users in marketing pretty much do the same.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One issue we keep running into is user A opening a story map to edit, and user B deciding to do the same, and well... whoever saves last... determines the outcome, overwriting the poor other users' edits. Sadly they occasionally only find this out right as they are about to go on a big screen in front of a crowd...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We'd like it to be that these storymaps could be either:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Version managed with merge/roll back functionality&lt;/LI&gt;&lt;LI&gt;Multi-user edit&lt;/LI&gt;&lt;LI&gt;Prevent-overwrite (such as classic network shared MS Office files: "this is open for edit by user X, you can not save changes")&lt;/LI&gt;&lt;/UL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Mar 2018 08:45:35 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-storymaps-ideas/storymap-cascade-multi-user-edit-and-or-check-in/idi-p/923466</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2018-03-07T08:45:35Z</dc:date>
    </item>
    <item>
      <title>Re: Storymap (cascade): Multi-user edit and/or check-in/check-out mechanism</title>
      <link>https://community.esri.com/t5/arcgis-storymaps-ideas/storymap-cascade-multi-user-edit-and-or-check-in/idc-p/923467#M8</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It appears this is still an issue with the latest NEW storymaps. I'm looking for this type of functionality so that my researchers can collaborate with their research assistants when creating story maps....unless we go back to classic?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 23 Jan 2020 16:47:08 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-storymaps-ideas/storymap-cascade-multi-user-edit-and-or-check-in/idc-p/923467#M8</guid>
      <dc:creator>SharonJanzen</dc:creator>
      <dc:date>2020-01-23T16:47:08Z</dc:date>
    </item>
    <item>
      <title>Re: Storymap (cascade): Multi-user edit and/or check-in/check-out mechanism - Status changed to: Closed</title>
      <link>https://community.esri.com/t5/arcgis-storymaps-ideas/storymap-cascade-multi-user-edit-and-or-check-in/idc-p/1223507#M1257</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Closing this idea since the classic Cascade template is in extended support and will not be enhanced with any new features.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;ArcGIS StoryMaps presents a warning when multiple authors are editing at the same time.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Oct 2022 18:51:03 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-storymaps-ideas/storymap-cascade-multi-user-edit-and-or-check-in/idc-p/1223507#M1257</guid>
      <dc:creator>OwenGeo</dc:creator>
      <dc:date>2022-10-19T18:51:03Z</dc:date>
    </item>
  </channel>
</rss>

