<?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: Caius Duthie</title>
    <description>The latest articles on DEV Community by Caius Duthie (@caiusduthie).</description>
    <link>https://dev.to/caiusduthie</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%2F4240375%2F4feb89b0-07c4-43af-be38-cf31197e6f75.jpg</url>
      <title>DEV Community: Caius Duthie</title>
      <link>https://dev.to/caiusduthie</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/caiusduthie"/>
    <language>en</language>
    <item>
      <title>A Small Spreadsheet That Makes Habitat Notes Easier to Revisit</title>
      <dc:creator>Caius Duthie</dc:creator>
      <pubDate>Thu, 12 Nov 2026 07:12:18 +0000</pubDate>
      <link>https://dev.to/caiusduthie/a-small-spreadsheet-that-makes-habitat-notes-easier-to-revisit-1o93</link>
      <guid>https://dev.to/caiusduthie/a-small-spreadsheet-that-makes-habitat-notes-easier-to-revisit-1o93</guid>
      <description>&lt;p&gt;After a wet afternoon outdoors, field notes can look more like a puzzle than a record. One person writes a bird name, another records a sound, and somebody photographs the same corner three times. I would rather keep those observations useful than ask volunteers to learn a complicated new system.&lt;/p&gt;

&lt;p&gt;My starting point is a small spreadsheet. Each row holds one observation. The columns answer ordinary questions: when, where, what, who recorded it, and how certain are we? A separate notes column gives people room to explain an uncertainty without squeezing it into an identification field.&lt;/p&gt;

&lt;p&gt;Why use a spreadsheet at all? It is easy to share, easy to export and familiar enough that another person can take over. A clever database can wait. The first test is whether someone returning from a walk can add a row without calling the person who built the file.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpwpj54bxuejufgjw5d5l.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fpwpj54bxuejufgjw5d5l.jpg" alt="A small set of consistent columns can make field notes easier to revisit." width="800" height="534"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I would give each observation a simple reference number. A photograph can use the same reference in its filename. That small habit saves a surprising amount of searching later. It also lets the record point to an image without putting a large photograph inside every spreadsheet cell.&lt;/p&gt;

&lt;p&gt;A short script can handle the dull checks. It can flag an empty date, a repeated reference number or a location that has been typed three different ways. The script should produce a review list and leave the original rows alone. A warning is an invitation to look again, not permission to rewrite somebody’s observation.&lt;/p&gt;

&lt;p&gt;Uncertainty deserves its own place. A drop-down with options such as certain, likely and unknown can help, provided everyone understands what those words mean. I would keep the original description too. Software cannot turn a hurried glimpse of a brown bird into a reliable species record.&lt;/p&gt;

&lt;p&gt;For community projects, a useful summary might be a monthly list of places visited and questions still open. It does not need an impressive dashboard. A filter showing records that need a second look may do more for the next walk than a colourful chart of uncertain sightings.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9lu8v1knr5wjezig8z47.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F9lu8v1knr5wjezig8z47.jpg" alt="Keep tools simple enough to use outdoors and hand over to another volunteer." width="800" height="534"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Before sharing the file, check what it reveals. Volunteer contact details belong elsewhere. Exact locations for sensitive wildlife may also need a different approach from a public map. Ask the organisation managing the records how it wants those details handled, rather than building assumptions into the export.&lt;/p&gt;

&lt;p&gt;The handover matters as much as the script. Put a short explanation beside the file: what each column means, how to add a record, how to run the checks and where the backup lives. Then ask someone else to try it while you keep quiet.&lt;/p&gt;

&lt;p&gt;I like tools that make the next conversation easier. If a spreadsheet helps a group remember what it noticed, admit what it does not know and choose a useful question for another walk, it has earned its place.&lt;/p&gt;

&lt;p&gt;The best first version is often deliberately small: one file, a handful of clear checks and a colleague who can explain the result without needing its original author.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>software</category>
      <category>tools</category>
    </item>
  </channel>
</rss>
