<?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>topic Re: Spring Clean in ArcGIS Online Questions</title>
    <link>https://community.esri.com/t5/arcgis-online-questions/spring-clean/m-p/1506635#M60320</link>
    <description>&lt;P&gt;A clean slate sounds nice, but the risk of breaking something is pretty high. Even if you add things back, everything will get a new ItemID, and any prior links or map configurations will not work.&lt;/P&gt;&lt;P&gt;We're not a big org, but here's how we approach it. You can use the built-in Administrative Reports, or else use Python, but every month or so, get a list of all your portal's content, along with how many views the item has had. Keep generating these reports, and after several months, you can combine reports into a single dataset.&lt;/P&gt;&lt;P&gt;At that point, you've got your items and their view count per month. You can calculate how much an item is being used month-over-month and get a derived percentage.&lt;/P&gt;&lt;P&gt;For items that are not being viewed (e.g., the growth percent is 0, no new views are coming in), you can more safely assume that these items are "stale". I would suggest establishing a formal policy in your organization that items which remain "stale" for more than, say, 6 consecutive months, will be archived and removed from the site.&lt;/P&gt;&lt;P&gt;This gives your users a clear metric and a policy to back up any decisions to remove content from the site. You can fine-tune the idea however you like.&lt;/P&gt;</description>
    <pubDate>Thu, 18 Jul 2024 14:13:15 GMT</pubDate>
    <dc:creator>jcarlson</dc:creator>
    <dc:date>2024-07-18T14:13:15Z</dc:date>
    <item>
      <title>Spring Clean</title>
      <link>https://community.esri.com/t5/arcgis-online-questions/spring-clean/m-p/1506614#M60315</link>
      <description>&lt;P&gt;We are concerned that across our hundreds of users a lot of data has been created that is not being actively used. Many of these files have a tiny storage cost implication but cumulatively it is very significant.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Asking users to review their content isn't always practical, so i wonder whether periodically we should download all data from ArcGIS Online and wipe the slate clean. Users could then add back the data they actually need.&lt;/P&gt;&lt;P&gt;How have other large organisations dealt with this?&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jul 2024 13:40:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-questions/spring-clean/m-p/1506614#M60315</guid>
      <dc:creator>OliverIshmael</dc:creator>
      <dc:date>2024-07-18T13:40:52Z</dc:date>
    </item>
    <item>
      <title>Re: Spring Clean</title>
      <link>https://community.esri.com/t5/arcgis-online-questions/spring-clean/m-p/1506635#M60320</link>
      <description>&lt;P&gt;A clean slate sounds nice, but the risk of breaking something is pretty high. Even if you add things back, everything will get a new ItemID, and any prior links or map configurations will not work.&lt;/P&gt;&lt;P&gt;We're not a big org, but here's how we approach it. You can use the built-in Administrative Reports, or else use Python, but every month or so, get a list of all your portal's content, along with how many views the item has had. Keep generating these reports, and after several months, you can combine reports into a single dataset.&lt;/P&gt;&lt;P&gt;At that point, you've got your items and their view count per month. You can calculate how much an item is being used month-over-month and get a derived percentage.&lt;/P&gt;&lt;P&gt;For items that are not being viewed (e.g., the growth percent is 0, no new views are coming in), you can more safely assume that these items are "stale". I would suggest establishing a formal policy in your organization that items which remain "stale" for more than, say, 6 consecutive months, will be archived and removed from the site.&lt;/P&gt;&lt;P&gt;This gives your users a clear metric and a policy to back up any decisions to remove content from the site. You can fine-tune the idea however you like.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jul 2024 14:13:15 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-questions/spring-clean/m-p/1506635#M60320</guid>
      <dc:creator>jcarlson</dc:creator>
      <dc:date>2024-07-18T14:13:15Z</dc:date>
    </item>
    <item>
      <title>Re: Spring Clean</title>
      <link>https://community.esri.com/t5/arcgis-online-questions/spring-clean/m-p/1506701#M60326</link>
      <description>&lt;P&gt;No this is not practical and is an anti-workflow.&lt;/P&gt;&lt;P&gt;Start with user training. If they want an account, they do training and get guidelines. This is the quickest and most effective solution but I appreciate not as easy after the users have all been provided access...&lt;/P&gt;&lt;P&gt;For administration start with identifying the items and users. Here's a guide on understanding storage and credits:&lt;/P&gt;&lt;P&gt;&lt;A href="https://esriaustraliatechblog.wordpress.com/2021/06/22/which-arcgis-online-items-are-consuming-the-most-credits-through-storage/" target="_blank"&gt;https://esriaustraliatechblog.wordpress.com/2021/06/22/which-arcgis-online-items-are-consuming-the-most-credits-through-storage/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;From there it's a bit more dependant on your organisation and needs but you could look at different aspects to identify if it's in use or not:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Item sharing&lt;/LI&gt;&lt;LI&gt;Authoritative tags&lt;/LI&gt;&lt;LI&gt;Usage&lt;/LI&gt;&lt;LI&gt;Metadata completion&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;There are some reporting tools inbuilt but can be further extended by python.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jul 2024 15:42:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-questions/spring-clean/m-p/1506701#M60326</guid>
      <dc:creator>ChristopherCounsell</dc:creator>
      <dc:date>2024-07-18T15:42:47Z</dc:date>
    </item>
  </channel>
</rss>

