The latest articles on DEV Community by Jack Jay (@theguysaccount). https://dev.to/theguysaccount 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%2F4242894%2F90c6f972-bdb4-463a-a1db-71406243f106.jpg https://dev.to/theguysaccount en Jack Jay Fri, 13 Nov 2026 12:13:49 +0000 https://dev.to/theguysaccount/how-to-identify-meeting-notetakers-with-an-open-dataset-21dj https://dev.to/theguysaccount/how-to-identify-meeting-notetakers-with-an-open-dataset-21dj <p>A meeting participant called “Notetaker” tells you surprisingly little. It might be a calendar guest, a built-in feature of the call platform, or a separate recorder that never appears in the participant list. Those cases require different controls. A name match is a starting point for review.</p> <p>We published a <a href="https://fliclabs.github.io/ai-notetakers/" rel="noopener noreferrer">dataset of 90 meeting notetakers</a> at Meetful. The records describe how each tool joins and link to the vendor instructions. You can download the <a href="https://fliclabs.github.io/ai-notetakers/notetakers.json" rel="noopener noreferrer">JSON</a> or <a href="https://fliclabs.github.io/ai-notetakers/notetakers.csv" rel="noopener noreferrer">CSV</a>.</p> <h2> Check how a tool joins </h2> <ol> <li><p>If it joins as a participant, start with the participant list and the calendar invite. Removing it from the call and changing future auto-join settings are separate actions.</p></li> <li><p>If it’s built into the platform, look for the relevant recording, transcription, or assistant controls for your role and account.</p></li> <li><p>If it records locally, the participant list may offer no signal. Ask how notes are being captured and agree on what can be shared before the conversation starts.</p></li> </ol> <h2> Pull the records into a review tool </h2> <div class="highlight js-code-highlight"> <pre class="highlight shell"><code>curl -fsSL https://fliclabs.github.io/ai-notetakers/notetakers.json <span class="o">|</span> jq -r <span class="s1">'.notetakers[] | [.name, .kind, .page] | @tsv'</span> </code></pre> </div> <p>For an internal directory, keep the source URLs next to each entry. Treat a missing value as unknown. If you flag a participant by name, make the alert reviewable by a human: names can change, and some recording methods never show up as a participant.</p> <p>I build <a href="https://meetful.com/?utm_source=devto&amp;utm_medium=referral" rel="noopener noreferrer">Meetful</a>. The <a href="https://meetful.com/notetakers" rel="noopener noreferrer">browser directory</a> includes the per-tool instructions and vendor sources for checking individual cases.</p> <p><em>AI assistance was used to draft this article.</em></p> ai data opensource tools