<?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 AGO - Archive content in ArcGIS Online Ideas</title>
    <link>https://community.esri.com/t5/arcgis-online-ideas/ago-archive-content/idi-p/953755</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Business case for archiving content hosted in AGO.&amp;nbsp; Archiving/un-archiving vs deleting/recreating.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data (hosted feature and tile services) storage is the biggest cost.&amp;nbsp; When projects are shelved for extended periods of time, but not necessarily permanently in which case content could just be deleted, it would be useful to be able to tag an app or a map as "archived".&amp;nbsp; All hosted content referenced by the app, and owned by the same owner of the app could also be automatically tagged as archived.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Content tagged as archived would then be disabled (unaccessible) and charged a reduced rate for service credits. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Archived content could be easily un-archived/made accessible.&amp;nbsp; Organizations would realize a credit saving for archived content and maximize good use of staff time.&amp;nbsp; Archiving could be more efficient than republishing content and rebuilding maps and apps if content was deleted and project needed to be recreated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The notion of archiving could also be useful for audit or record requirements.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 22 Jun 2016 17:55:10 GMT</pubDate>
    <dc:creator>MegHoole2</dc:creator>
    <dc:date>2016-06-22T17:55:10Z</dc:date>
    <item>
      <title>AGO - Archive content</title>
      <link>https://community.esri.com/t5/arcgis-online-ideas/ago-archive-content/idi-p/953755</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Business case for archiving content hosted in AGO.&amp;nbsp; Archiving/un-archiving vs deleting/recreating.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data (hosted feature and tile services) storage is the biggest cost.&amp;nbsp; When projects are shelved for extended periods of time, but not necessarily permanently in which case content could just be deleted, it would be useful to be able to tag an app or a map as "archived".&amp;nbsp; All hosted content referenced by the app, and owned by the same owner of the app could also be automatically tagged as archived.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Content tagged as archived would then be disabled (unaccessible) and charged a reduced rate for service credits. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Archived content could be easily un-archived/made accessible.&amp;nbsp; Organizations would realize a credit saving for archived content and maximize good use of staff time.&amp;nbsp; Archiving could be more efficient than republishing content and rebuilding maps and apps if content was deleted and project needed to be recreated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The notion of archiving could also be useful for audit or record requirements.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 22 Jun 2016 17:55:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-ideas/ago-archive-content/idi-p/953755</guid>
      <dc:creator>MegHoole2</dc:creator>
      <dc:date>2016-06-22T17:55:10Z</dc:date>
    </item>
    <item>
      <title>Re: AGO - Archive content</title>
      <link>https://community.esri.com/t5/arcgis-online-ideas/ago-archive-content/idc-p/1069351#M8042</link>
      <description>&lt;P&gt;Additionally if it's too difficult/costly for esri to store online, provide the ability to download to disk, and then easily upload and restore at a later point. I had a project&amp;nbsp; that closed. It leveraged a webmap that eventually got removed because it was actively being used. However, I later needed to restore it to show it off for marketing purposes, and it wasn't worth the effort to do so. This is one of several valid use cases.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jun 2021 14:10:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-ideas/ago-archive-content/idc-p/1069351#M8042</guid>
      <dc:creator>MichaelRutkowski</dc:creator>
      <dc:date>2021-06-17T14:10:30Z</dc:date>
    </item>
    <item>
      <title>Re: AGO - Archive content</title>
      <link>https://community.esri.com/t5/arcgis-online-ideas/ago-archive-content/idc-p/1199376#M9186</link>
      <description>&lt;P&gt;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/129401"&gt;@KoryKramer&lt;/a&gt;&amp;nbsp; I think this idea is very close to my &lt;A href="https://community.esri.com/t5/arcgis-online-ideas/allow-agol-to-archive-story-maps/idi-p/924832" target="_self"&gt;idea&lt;/A&gt;&amp;nbsp;and a candidate for merging, if you feel appropriate.&lt;/P&gt;&lt;P&gt;I would like to expand on this by saying it would be good to archive experience builder sites along with their data. In my idea I envisage some button that packages up the entire folder of data, web maps, survey 123 forms and the experience builder site into a single package file which I can then download and archive locally allowing me to remove the data/site off AGOL.&lt;/P&gt;&lt;P&gt;There should also be an equivalent upload of the package to allow the site to be unpacked and made available again.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Aug 2022 14:05:43 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-ideas/ago-archive-content/idc-p/1199376#M9186</guid>
      <dc:creator>DuncanHornby</dc:creator>
      <dc:date>2022-08-04T14:05:43Z</dc:date>
    </item>
  </channel>
</rss>

