<?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: How to store historic or archived data. in Data Management Questions</title>
    <link>https://community.esri.com/t5/data-management-questions/how-to-store-historic-or-archived-data/m-p/1199603#M44139</link>
    <description>&lt;P&gt;If you have access to a maintenance account you could explore the archiving workflows shown in this web course:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.esri.com/training/catalog/57630435851d31e02a43efb0/archiving-data-in-a-multiuser-geodatabase/" target="_blank"&gt;https://www.esri.com/training/catalog/57630435851d31e02a43efb0/archiving-data-in-a-multiuser-geodatabase/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 04 Aug 2022 20:26:35 GMT</pubDate>
    <dc:creator>ClaudioRuschel</dc:creator>
    <dc:date>2022-08-04T20:26:35Z</dc:date>
    <item>
      <title>How to store historic or archived data.</title>
      <link>https://community.esri.com/t5/data-management-questions/how-to-store-historic-or-archived-data/m-p/1199459#M44137</link>
      <description>&lt;P&gt;I have a group that has a boundary feature that they update on an annual basis. These boundaries are used to determine permits and applications for that year. I am wondering how to make an authoritative dataset for this type of data, that changes on an annual basis, but previous versions of the data are still relevant. I would like to maintain the most current boundary on Enterprise, and have that published and available publicly, but am not sure I want to be maintaining multiple very similar boundaries.&lt;/P&gt;&lt;P&gt;How do other organizations handle and organize data of this nature? Currently we have file geodatabases in "archival" folders that are read only to hold the previous iterations of the data, with the newest boundary being saved on Enterprise.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Aug 2022 16:21:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/how-to-store-historic-or-archived-data/m-p/1199459#M44137</guid>
      <dc:creator>Anonymous User</dc:creator>
      <dc:date>2022-08-04T16:21:13Z</dc:date>
    </item>
    <item>
      <title>Re: How to store historic or archived data.</title>
      <link>https://community.esri.com/t5/data-management-questions/how-to-store-historic-or-archived-data/m-p/1199465#M44138</link>
      <description>&lt;P&gt;I would consider using a &lt;STRONG&gt;Parcel Fabric&lt;/STRONG&gt; dataset. It has built-in capabilities for tracking historic changes, and makes it very easy to create an attribute-based filter to only show current features. It's meant more for cadastral boundaries, but there's no reason you couldn't use it for something a bit more general.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Aug 2022 16:31:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/how-to-store-historic-or-archived-data/m-p/1199465#M44138</guid>
      <dc:creator>jcarlson</dc:creator>
      <dc:date>2022-08-04T16:31:10Z</dc:date>
    </item>
    <item>
      <title>Re: How to store historic or archived data.</title>
      <link>https://community.esri.com/t5/data-management-questions/how-to-store-historic-or-archived-data/m-p/1199603#M44139</link>
      <description>&lt;P&gt;If you have access to a maintenance account you could explore the archiving workflows shown in this web course:&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.esri.com/training/catalog/57630435851d31e02a43efb0/archiving-data-in-a-multiuser-geodatabase/" target="_blank"&gt;https://www.esri.com/training/catalog/57630435851d31e02a43efb0/archiving-data-in-a-multiuser-geodatabase/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Aug 2022 20:26:35 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/how-to-store-historic-or-archived-data/m-p/1199603#M44139</guid>
      <dc:creator>ClaudioRuschel</dc:creator>
      <dc:date>2022-08-04T20:26:35Z</dc:date>
    </item>
    <item>
      <title>Re: How to store historic or archived data.</title>
      <link>https://community.esri.com/t5/data-management-questions/how-to-store-historic-or-archived-data/m-p/1249003#M44362</link>
      <description>&lt;P&gt;Some other resources you may want to check out include...&lt;/P&gt;&lt;P&gt;ArcGIS Pro archiving help doc -&amp;nbsp;&lt;A href="https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/what-is-archiving-.htm" target="_blank"&gt;https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/what-is-archiving-.htm&lt;/A&gt;&amp;nbsp;and a blog series on archiving&amp;nbsp;&lt;A href="https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/maintain-data-accountability-with-archiving-part-2/" target="_blank"&gt;https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/maintain-data-accountability-with-archiving-part-2/&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 18 Jan 2023 11:49:46 GMT</pubDate>
      <guid>https://community.esri.com/t5/data-management-questions/how-to-store-historic-or-archived-data/m-p/1249003#M44362</guid>
      <dc:creator>DonaldRees</dc:creator>
      <dc:date>2023-01-18T11:49:46Z</dc:date>
    </item>
  </channel>
</rss>

