<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: DataCheck Research</title>
    <description>The latest articles on DEV Community by DataCheck Research (@datacheckresearch).</description>
    <link>https://dev.to/datacheckresearch</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4111365%2F107b6048-271b-4836-97a0-ecd8b65b2337.png</url>
      <title>DEV Community: DataCheck Research</title>
      <link>https://dev.to/datacheckresearch</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/datacheckresearch"/>
    <language>en</language>
    <item>
      <title>Publishing an auditable company-trends dataset: what we chose to expose</title>
      <dc:creator>DataCheck Research</dc:creator>
      <pubDate>Sat, 05 Sep 2026 16:07:13 +0000</pubDate>
      <link>https://dev.to/datacheckresearch/publishing-an-auditable-company-trends-dataset-what-we-chose-to-expose-35b6</link>
      <guid>https://dev.to/datacheckresearch/publishing-an-auditable-company-trends-dataset-what-we-chose-to-expose-35b6</guid>
      <description>&lt;p&gt;Open data is most useful when it is not merely downloadable, but explainable.&lt;/p&gt;

&lt;p&gt;At DataCheck Research, we publish a small, reusable dataset of Israeli company-registration and status-change trends. The objective is not to claim that one monthly count explains the economy. It is to make a constrained question reproducible: what changed in the register, when, and according to which sources?&lt;/p&gt;

&lt;h2&gt;
  
  
  The modelling choice
&lt;/h2&gt;

&lt;p&gt;A registration date, a dissolution event and a registry status update are not interchangeable. In particular, an update appearing in a public register may lag the legal event behind it. Treating all status changes as the same event creates a chart that looks decisive but is methodologically weak.&lt;/p&gt;

&lt;p&gt;We therefore keep separate series for registrations and status changes, document their provenance, and label the combined series as a &lt;em&gt;net-movement proxy&lt;/em&gt; rather than a census of operating businesses.&lt;/p&gt;

&lt;h2&gt;
  
  
  What a reusable public dataset needs
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Provenance.&lt;/strong&gt; Every series should lead back to its source and extraction method.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Scope.&lt;/strong&gt; State what the record represents and what it does not.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Stable fields.&lt;/strong&gt; A lightweight CSV is often more durable than a dashboard-only chart.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Citation.&lt;/strong&gt; Reuse should preserve visible attribution to the original source.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A human explanation.&lt;/strong&gt; Metadata is not a substitute for a method note.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The repository includes CSV files, methodology, contribution guidance and a citation file. It is released under CC BY 4.0: reuse is welcome with visible credit and a link back to the source.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Dataset and methodology: &lt;a href="https://github.com/DataCheckResearch/israel-company-trends-data" rel="noopener noreferrer"&gt;https://github.com/DataCheckResearch/israel-company-trends-data&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Interactive company trends: &lt;a href="https://datacheck.co.il/trends" rel="noopener noreferrer"&gt;https://datacheck.co.il/trends&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A public dataset earns trust when a skeptical reader can understand where it came from, what changed, and where its limits are.&lt;/p&gt;

&lt;h1&gt;
  
  
  opendata #datascience #research #dataviz
&lt;/h1&gt;

</description>
      <category>analysis</category>
      <category>analytics</category>
      <category>data</category>
    </item>
  </channel>
</rss>
