<?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 Inconsistency and redundancy in Developers Questions</title>
    <link>https://community.esri.com/t5/developers-questions/inconsistency-and-redundancy/m-p/776385#M5257</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;While I still only have little experience in the GIS world, I do have some experience in developing administrative applications. When using a RDMS like SQL server I always try to avoid redundant data, because it can lead to inconsistency. In the short time I have worked with GIS Ive seen&amp;nbsp;multiple examples on "Colletor" apps where the user added new attributes to a feature class (which really doesnt belong there) and the "developers" then created a windows scheduled task to copy the some of the data to another feature class. As an application developer it really hurts to see, and I belive that the users either are using "Collector" wrong og using it for something it wasnt supposed to be used for.&lt;/P&gt;&lt;P&gt;Am I wrong? Is it acceptable to change the datamodel to fit a soloution made in a generic tool? Is it&amp;nbsp;&lt;SPAN&gt;acceptable&amp;nbsp;you have to use windows scheduled task to syncronize data between feature classes?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 24 Sep 2019 12:19:20 GMT</pubDate>
    <dc:creator>leonoestergaard</dc:creator>
    <dc:date>2019-09-24T12:19:20Z</dc:date>
    <item>
      <title>Inconsistency and redundancy</title>
      <link>https://community.esri.com/t5/developers-questions/inconsistency-and-redundancy/m-p/776385#M5257</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;While I still only have little experience in the GIS world, I do have some experience in developing administrative applications. When using a RDMS like SQL server I always try to avoid redundant data, because it can lead to inconsistency. In the short time I have worked with GIS Ive seen&amp;nbsp;multiple examples on "Colletor" apps where the user added new attributes to a feature class (which really doesnt belong there) and the "developers" then created a windows scheduled task to copy the some of the data to another feature class. As an application developer it really hurts to see, and I belive that the users either are using "Collector" wrong og using it for something it wasnt supposed to be used for.&lt;/P&gt;&lt;P&gt;Am I wrong? Is it acceptable to change the datamodel to fit a soloution made in a generic tool? Is it&amp;nbsp;&lt;SPAN&gt;acceptable&amp;nbsp;you have to use windows scheduled task to syncronize data between feature classes?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 24 Sep 2019 12:19:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/developers-questions/inconsistency-and-redundancy/m-p/776385#M5257</guid>
      <dc:creator>leonoestergaard</dc:creator>
      <dc:date>2019-09-24T12:19:20Z</dc:date>
    </item>
  </channel>
</rss>

