Here’s a DNA‑aware version of your Zotero “Research Plan + Control” template, keeping GPS in view while adding match‑ and test‑specific structure.familysearch+3.
You'll find here templates for using Ancestry, MyHeritage and FTDNA (including mtDNA) as well as tag set for all three platforms is.
Create project libraries, collections per case study, and notes for research questions, plans, and logs, all linked to your sources and citations. A documented workflow uses subcollections and standardized notes (“Research Control” note, GPS tags, saved searches) to keep plans, evidence, and proof arguments in one coherent structure.
Here’s a concrete Zotero-centered structure you can drop your research plans into, using things you already know how to drive.libnet+3
Create one top-level collection per research project or key person, with subcollections for Plan, Evidence, and Writing (or your preferred 00–10 structure).organizeyourfamilyhistory+2
Use notes and tags—rather than new item types—to store the research plan and link it directly to the sources and to your research log.genohistory+2
Collection = project container (e.g., “Clark – Identify parents of X, Muskogee Co.”), mirroring the “individual collection + subcollections” pattern described in current genealogy workflows.reddit+1
Standalone note “Research Control / Plan” = your master research question, objective, and step list, which you can duplicate as a template for new projects (Better Notes helps if you want structured templates).libnet
Child notes on individual sources = mini-log entries attached to each Zotero item, capturing search details, extracted evidence, and correlation comments.genohistory+1
Tags = status (to do, in progress, completed), GPS-related tags (e.g., gps:plan, gps:analysis, gps:proof), family line, locality.zotero+1
Within a project collection:
00 – Plan & Control
Master “Research Plan + Control” note
Optional: a separate “Questions/Future To-Do” note
10 – Sources to Check
Empty items created in advance with titles like “FS film 123456 – Muskogee Co. deeds 1900–1910 (TO DO)”
20 – Evidence Collected
Items with attached images/PDFs for records you’ve captured
30 – Analysis & Correlation
Notes for timelines, correlation tables, FAN analysis
40 – Writing & Reports
Draft proof summaries, report sections, blog outlines
The 00–40 idea follows documented “individual collection + subcollections + control note” workflows other genealogists are using successfully.youtubezotero+1
Use a single rich-text note (Better Notes if you want outlines) with something like:
Objective: one-sentence research question.
Background summary: 3–6 bullets, with Zotero citekeys or links back to items.
Working hypothesis: 1–2 sentences.
Planned steps: numbered list, each step including: record type, repository/site, target names/dates/places, and a Zotero link to the “placeholder” item in 10 – Sources to Check.
Status: a small table (Step / Status / Result note / Date) you update as you work.
Zotero-based handouts emphasize using such “control” notes and tags to replace traditional research logs and to‑do lists while keeping everything in one place.genohistory+2
Open the project collection and its “Research Plan + Control” note.
For each planned step, create a Zotero item (if not already there) and tag it status: to-do.
When you work the step, open the item, attach any image/PDF, and create a child note recording: search terms, scope, positive/negative results, and extracted evidence.
Update the status tag (in-progress, then done) and add a brief summary back into the control note under that step.
Use saved searches (e.g., status: to-do + collection = this project) as your live “research plan view.”reddit+2
Here’s a reusable blank “Research Plan + Control” template you can paste into a new Zotero note and save as your standard project template.
[State the research question in one precise sentence, including identity, relationship, time, and place.]
[Fact 1 with brief citation or note and link to Zotero item.]
[Fact 2 with brief citation or note and link to Zotero item.]
[Fact 3 with brief citation or note and link to Zotero item.]
[Prior negative searches, summarized briefly, with link(s) to negative‑search notes.]
[Write 1–3 sentences describing your current best hypothesis. Acknowledge uncertainty.]
[For each step, you can later add a link to a prepared Zotero item and status tags.]
[Short label for step 1]
Record type / jurisdiction: [e.g., marriage, probate, land; county/state/country.]
Repository / access: [archive, courthouse, website, microfilm, etc.]
Target: [Who/what you are trying to find; names, date range, locality.]
Method note: [Search strategy, key variants, FAN focus, etc.]
Linked Zotero item: [paste item link when created]
Status: [to‑do / in progress / done]
[Short label for step 2]
Record type / jurisdiction: [...]
Repository / access: [...]
Target: [...]
Method note: [...]
Linked Zotero item: [...]
Status: [...]
[Short label for step 3]
Record type / jurisdiction: [...]
Repository / access: [...]
Target: [...]
Method note: [...]
Linked Zotero item: [...]
Status: [...]
[Continue steps 4–10+ as needed, grouping by record type or repository.]
[Add or remove rows as needed.]
[Question or uncertainty 1 you want to keep in view.]
[Question or uncertainty 2.]
[Possible future avenue (different locality, associated family, record type).]
To turn this into a reusable template, you can:
Save a copy of this note in a “Templates” collection and duplicate it for each new project.
Or use your preferred Zotero note add‑on to register it as a named template and insert it into any project note.
_____________________________________________________________________________
Here’s a compact “micro‑plan” control note template for a single repository visit or focused session. Use it alongside the full template rather than instead of it.
[One sentence: what you want to accomplish in this specific visit/session.]
Example: “Identify all probate files for men named Clark in Muskogee County between 1870 and 1905.”
Project: [link to main project collection or control note.]
Repository / website: [name, URL, catalog link.]
Date & time available: [e.g., 2026‑04‑03, 3 hours.]
[Task 1 short label]
Collection / call no. / URL: [exact reference where possible.]
Record type: [probate index, deed index, microfilm X, database Y, etc.]
Search target: [names, date range, locality, variants.]
Output: [what you will capture—images, abstracts, full transcriptions, negative search note.]
Linked Zotero item: [paste when created.]
Status: [to‑do / in progress / done]
[Task 2 short label]
Collection / call no. / URL: [...]
Record type: [...]
Search target: [...]
Output: [...]
Linked Zotero item: [...]
Status: [...]
[Task 3 short label]
Collection / call no. / URL: [...]
Record type: [...]
Search target: [...]
Output: [...]
Linked Zotero item: [...]
Status: [...]
[Add more tasks as needed; aim for what you can realistically do in the time.]
[Follow‑up 1, e.g., “Attach images to main Zotero items and create child notes with full abstracts.”]
[Follow‑up 2, e.g., “Update main control note research plan status for steps 3 and 4.”]
[Follow‑up 3, e.g., “Schedule second visit for unexamined volumes.”]
You can keep a master copy of this “micro‑plan” in a Templates collection, then duplicate and adapt it each time you plan a focused session.
The last two weeks on forums.zotero.org have been dominated by Zotero 8–related feature announcements, new beta features, and a significant Better BibTeX bug that silently touched “Date Modified” on large libraries. For a working genealogist, the most relevant threads touch on: how safe your timestamps and item keys are, new ways to track “who did what” in group projects, experimental “Recently Read” views, and plugins that make annotation cross‑linking and semantic search more powerful in a research-log style workflow.zotero+1
Zotero 8 maturation and faster releases. A general “Announcing Zotero 8” thread and a companion “faster release cycle” discussion frame the current moment: changes are arriving more quickly, including field schema changes and new reader features. For genealogists, that means plugin breakage (BBT, notes tools, automation) is more likely in the short term but also that long‑requested research-automation features land sooner.zotero
New beta features for reading and collaboration. Several pinned “Available for beta testing” threads introduce: a Recently Read collection, Added By/Modified By fields in group libraries, Read Aloud, and the ability to add annotations directly to word processor documents. Each of these can map directly to evidence review, teaching, and collaborative project tracking in genealogical work.zotero
Beta annotation tools let you add notes straight to Word docs—ideal for transcribing census records or linking evidence in family timelines. The AI suggestion thread highlights plugins for PDF chatting, perfect for querying scanned genealogy docs like wills or letters. "Recently Read" and group tracking help manage research logs across collaborative family projects or workshops.
A new “Recently Read collection” beta exposes a dynamic view of items you have opened or read most recently. For genealogy workflows that naturally bounce between tax lists, deeds, maps, and compiled genealogies, this is effectively an automated “working set” without needing to drag items into a temporary collection or maintain a manual “today’s log” collection.zotero
Implications for genealogical practice:
Keep the beta in mind as a substitute for a “scratch” collection when you are mid–brick-wall project and dipping into many sources without wanting to over-structure them prematurely.
Combined with saved searches (for example, items tagged with a case-study ID) this gives a quick way to return to “what I just looked at for John SMITH of X County” even after several days away.
Another beta adds “Added By” and “Modified By” fields for group libraries, visible as columns and usable in sorting/filtering. For genealogists working in society projects, one‑name studies, or family group projects, this is essentially a built‑in audit trail: who added that 1880 census, and who last edited the transcription note.zotero
Practical genealogy uses:
Assign responsibility in group research logs: sort by “Added By” when teaching volunteers, or by “Modified By” to review a student’s work in a case-study group library.
Use “Modified By” to check whether a citation style, tag schema, or note template has been consistently updated before generating a society report or proof argument.
The Read Aloud beta adds spoken reading of PDFs and (on some platforms) other content. For researchers with eye strain, low vision, or those who like to “listen through” long county histories or scholarly articles while making notes in parallel, this comp helps turn Zotero into more of an assistive-reading environment.zotero
In genealogical terms:
Use Read Aloud to skim long narrative sources (county histories, biographical compilations) while pausing to drop inline annotations that tie passages to specific individuals or hypotheses.
This also opens a practical path to reviewing older research reports you wrote years ago, listening for contradictions or gaps as you prepare updated narratives.
A fresh announcement describes a beta for adding annotations “directly to word processor documents.” While the technical details are still emerging, the upshot is tighter integration between Zotero’s reader annotations and your Word/Google Docs manuscript.zotero
For genealogists writing proof arguments, client reports, or society journal articles:
Expect a shorter path from highlighted evidence in Zotero’s reader to quoted or paraphrased material with citation scaffolding in your report.
This may reduce duplication between a “research log” note and the final narrative, since annotations can feed the writing tool more directly.
One of the most important practical threads for any power user is the report of a mass “Date Modified” reset, eventually traced to a Better BibTeX (BBT) bug.zotero
A user reported that nearly their entire local library showed the same “Date Modified” timestamp without having done batch edits; at first, they suspected Zotero 8 background processes.zotero
Zotero’s lead developer clarified that Zotero itself does not run such background edits and that no related bug had been seen; instead, the root cause was a BBT bug where a save operation failed to pass the skipDateModifiedUpdate flag.zotero
The BBT maintainer confirmed the bug affected versions 8.0.5 to 8.0.15 (released around 16–17 February 2026) and that 8.0.16 fixes it. Anyone running those versions with Zotero 7.0.32 or 8/9 could have had Date Modified silently overwritten during that window.zotero
Implications for genealogists:
Date fields as research-log proxies are fragile. If you have been relying heavily on “Date Modified” as a surrogate research log (“what did I touch yesterday on this line?”), this incident is a reminder to use explicit status tags and structured notes instead of system metadata as your primary audit trail.
If you use BBT, verify you are on 8.0.16 or later, and consider documenting your current tag/status schema in a pinned note so you can rebuild workflows even if system fields get disturbed.zotero
In a disaster case, the official remedy was to delete zotero.sqlite locally and re‑sync, at the cost of reimporting any recent locally‑only items (which themselves lose their historical Date Added/Modified). That trade‑off is important when weighing whether to reset after a large genealogical project.zotero
Two more technical discussions touch on semantic search and item keys:
A “Semantic Search Tool for Zotero – open‑source RAG with source attribution” thread describes an external tool that layers semantic search over a Zotero library. For genealogists, that suggests future workflows where you can ask “Which records mention a possible father in X County between 1820–1840?” across notes and attachments, rather than only keyword search.zotero
A “Creating a link to a specific Zotero item key” and “itemkey visibility” discussion focuses on stable item identifiers and linking. In genealogical practice, consistent, visible item keys are the backbone of cross‑system linking (e.g., from RootsMagic, Scrivener, Obsidian, or a research wiki back into Zotero).zotero
Tips emerging from these for a family historian:
Normalize a way to store Zotero item keys in your genealogy software (custom fields or notes) and test that clicking a zotero://select link reliably opens the right evidence item.zotero
Track the semantic-search conversation if you want to move toward question‑answer workflows over your corpus of notes, transcriptions, and images, especially as AI tools become more tightly integrated.
Among the less prominent but practically helpful items:
“Annotation Links — Clickable cross‑reference links between PDF annotations” introduces a plugin that lets you create clickable links between annotations. For genealogists, this is excellent for building evidence chains directly in the PDF: for example, link a marginal note on a tax list to a note on a deed that resolves an identity conflict.zotero
There are several translator, proxy, and ISBN-recognition threads that mostly affect academic users, but genealogists who rely heavily on non‑US ISBNs or who routinely import via institutional proxies may want to check those if they notice broken importing.zotero
Bringing it together for genealogy and family history use:
Reinforce explicit research logs. Instead of relying on Date Modified, treat tags like status: reviewed, status: conflict, and type: deed/tax/map as your primary organizing scheme; that way, a plugin mishap cannot erase your sense of progress.zotero+1
Experiment with Recently Read as a “Today’s Desk” view. Use the beta collection during intense project bursts and combine it with saved searches keyed to a person, couple, or FAN cluster to quickly re‑enter a case after a break.zotero
Lean into group audit fields for societies. If you manage society projects, flip on Added By/Modified By in group libraries and build a review rhythm: for example, once a week, sort by Modified By to spot where members have been working and where mentoring or citation cleanup is needed.zotero
Plan for better writing integration. As word processor annotation integration matures, think through how your current proof arguments might change if highlights and annotations flowed directly into your report template—a good time to standardize note headings like “Identity,” “Conflict,” and “Negative Evidence” in your annotations.static.libnet+1
Audit your plugin stack after each major Zotero bump. The BBT Date Modified incident is a strong reminder that each Zotero 8 point release should trigger a quick check of all genealogy‑relevant plugins (BBT, Better Notes, Actions & Tags, etc.), with a clear fall‑back plan for your most critical projects.static.libnet+1
If you would like, the next step could be a short, reusable “March 2026 Zotero 8 safety checklist for genealogists” you could drop straight into your AI-for-genealogy blog or workshop handouts.
You can use the AI Prompt Builder plus an external AI to standardize, de-duplicate, and reformat messy imported sources in RootsMagic 11. Below are ready-to-use prompt patterns you can copy and paste into the Prompt Builder and reuse.rootsmagic+1
Open any person, then open the AI Prompt Builder from the AI menu or person tools.rootsmagic+1
Choose to create a free-form prompt, then paste one of the prompt texts below into the editor.[help.rootsmagic]
In the options, decide whether to include that person’s events/relatives or leave the prompt generic; for pure source cleanup, you usually do not need person data included.rootsmagic+1
Save with a name like “Clean imported source,” “Normalize online tree citation,” or “Source template extractor,” then reuse it for any person or fact by selecting the prompt and clicking Copy.rootsmagic+1
Use this when you have a poorly formatted citation or source text pasted into a note or fact.
Prompt text (save as a reusable prompt):
Role: You are a professional genealogist and citation editor specializing in Evidence Explained–style citations. You will receive messy, imported source or citation text from RootsMagic.
Task:
Identify and correct obvious typos and spacing.
Standardize capitalization (title case for titles, sentence case for notes).
Expand abbreviations only when the meaning is clear (e.g., “Co.” → “County” when used in a place).
Separate the information into:
Source list entry (for RootsMagic “Master source” field).
Full reference note (first citation).
Subsequent reference note (short citation).
Do not invent missing details. If something is missing or unclear, write “[unknown]” or “[illegible]” rather than guessing.
Output format (use this exact structure):
Source list entry:
[one line]Full reference note:
[one paragraph]Subsequent reference note:
[one line]Here is the messy source text to clean and structure:
text<<<PASTE ROOTSMAGIC SOURCE OR CITATION TEXT HERE>>>
Use this when imports have long, redundant “Ancestry Family Tree” style citations.
Role: You are a professional genealogist. Your task is to normalize messy combined-source citations imported from online trees into RootsMagic.
Task:
Remove marketing or irrelevant phrases (e.g., “Ancestry Family Trees,” “online publication,” “Provo, Utah, USA” publisher boilerplate) unless needed for citation clarity.
Identify the underlying record type (census, vital record, city directory, etc.) and rephrase the citation so the record type is clear.
Extract and clearly label: database/collection name, jurisdiction, record type, year or range, and access URL (if present).
Create:
A cleaned “Master Source” text suitable for RootsMagic (collection-level).
A “Citation detail” template line showing how to plug in person-specific details (e.g., “line ___, dwelling ___, family ___”).
Do not invent missing fields; mark them with “[unknown]”.
Output format:
Master source:
[one line, collection-level]Citation detail pattern:
[one line showing structure for the specific citation]Cleaned example citation (for this person only):
[one paragraph]Here is the imported source text:
text<<<PASTE IMPORTED ANCESTRY / OTHER TREE SOURCE TEXT HERE>>>
Adapt this pattern to whichever built‑in template you are using (similar to the “Artifact, privately held” and “Newspaper, unidentified clipping” extraction prompts people are using with RM11).youtube+1
Role: You are a professional genealogist and forensic document analyzer. Your task is to extract structured data from the text that follows so that I can populate a specific RootsMagic 11 source template.
Template type: [e.g., “Census, U.S. Federal (online images)” or “Artifact, privately held”].
Task:
Extract values for these fields (use the exact labels and order):
Source name
Author / creator
Title or description
Jurisdiction (state, county, place)
Repository or website
Call number / URL / path (if any)
Item type (e.g., deed, certificate, clipping, artifact)
Date of record or event
Person(s) of interest
If a field is not present, output “[not stated]”.
Do not add facts that are not explicitly supported by the text.
Output format (exact headings):
Source name:
Author / creator:
Title / description:
Jurisdiction:
Repository / website:
Call number / URL / path:
Item type:
Date of record or event:
Person(s) of interest:
Notes: [any clarifying comments or uncertainties]Here is the text to analyze:
text<<<PASTE IMPORTED SOURCE OR CITATION TEXT HERE>>>
Once you have this output, you can copy–paste each field into the corresponding RM11 template fields.[youtube][help.rootsmagic]
Use this when imports have multiple near-identical master sources.
Role: You are a professional genealogist and data curator. Your task is to analyze multiple RootsMagic source descriptions that may represent the same underlying record collection.
Task:
Group the following source descriptions into clusters that refer to the same collection.
For each cluster, propose a single standardized “Master Source” label suitable for RootsMagic.
List which original descriptions belong to each cluster.
Do not guess; if you are unsure whether two items are the same, put them in separate clusters and mark them “possibly same collection.”
Output format:
Cluster 1 – Master Source label:
[proposed standard label]
Includes:
[original source text 1]
[original source text 2]
Cluster 2 – Master Source label:
[etc.]Here are the imported source descriptions (each separated by a blank line):
text<<<PASTE A LIST OF SOURCE TITLES / DESCRIPTIONS HERE>>>
You can then manually merge or retitle master sources in RM11 based on the clusters.[help.rootsmagic]
__________________________________
Here’s a tailored AI prompt you can use with the RootsMagic 11 “Website (with multiple databases)” template to clean imported sources and extract structured fields. You can save this as a reusable prompt in the AI Prompt Builder.[youtube][sqlitetoolsforrootsmagic]
Role: You are a professional genealogist and citation editor working to Evidence Explained standards. You will receive messy text from an online collection (e.g., Ancestry, FamilySearch, MyHeritage, Fold3) that should be cited in RootsMagic 11 using the “Website (with multiple databases)” source template.
Task:
Identify the specific database/collection on the site and treat it as the main source.
Clean the text (fix typos, spacing, capitalization) without changing meaning or adding facts.
Extract values for the RootsMagic “Website (with multiple databases)” template fields listed below.
If a field is not present or is unclear, output “[not stated]” and do not guess.
Fields to extract (Master Source level – the database):
Source name (recommended pattern: “[Year range] [Database title] – [Website title]”)
Database author / creator (organization or person)
Database title (collection name as given on the site)
Creation or owner (entity that created or owns the digital collection, if given)
Title of website (e.g., Ancestry, FamilySearch, MyHeritage, Fold3)
URL for database home page (stable collection-level link, not the person page if possible)
Item type (e.g., “database with images,” “database,” “digital images”)
Credit line (archive, microfilm provider, or original record holder, if stated)
Source text (brief description of what the database contains, including place and time span, based only on the provided text)
Source comment (notes on coverage, quality, or indexing caveats, if present)
Source reference number (any catalog number, film number, DGS number, or internal ID, if given)
Fields to extract (Citation / item of interest level – this person’s record):
Access type (e.g., “digital image,” “indexed database with images,” “indexed database”)
Access date (in form “Day Month Year,” e.g., “22 March 2026,” if present)
Item of interest (name of person of interest and key identifiers such as event type, date, and place, based only on the supplied text)
Website path or record URL (direct link to the individual record page, if given)
Notes about the specific item (any remarks specific to this person’s record, such as “image truncated,” “index only,” or “original language Spanish,” if stated)
Output format (use these exact headings and keep them in this order):
Master source – Website (with multiple databases)
Source name:
Database author / creator:
Database title:
Creation or owner:
Title of website:
URL (database home page):
Item type:
Credit line:
Source text:
Source comment:
Source reference number:Citation – Item of interest
Access type:
Access date:
Item of interest:
Record URL or path:
Item notes:Here is the text to analyze and clean (this may include an imported RootsMagic citation, collection description, and/or record page details):
text<<<PASTE IMPORTED ONLINE SOURCE / CITATION TEXT HERE>>>
You can then copy each output line into the corresponding fields in the “Website (with multiple databases)” template in RootsMagic 11, using one Master Source per collection and separate citations for each person’s record.wiki.rootsmagic+1
___________________________________
This one is tuned for the kind of work you’re doing. You can adapt wording for 1850–1950 and online vs microfilm.
Role: You are a professional genealogist and citation editor working to Evidence Explained standards. You will receive messy text describing a U.S. census record (often copied from an online tree or site). The record will be cited in RootsMagic 11 using an online‑database census template.
Task:
Identify the census year, country, state, county, and locality; identify whether the site provides images, an index only, or both.
Clean the text (fix typos, spacing, capitalization) without changing meaning or adding facts not stated in the text.
Treat the database or collection as the Master Source and the individual household/entry as the Citation.
Extract values for these fields. If a field is not present, output “[not stated]” and do not guess.
Master Source (collection-level – for RootsMagic “U.S. census, online images” template):
Source name (recommended: “[Year] U.S. census, [state] – [website]”)
Census year
Country
State or territory
Database / collection title (as given on the site)
Website title (Ancestry, FamilySearch, etc.)
Publisher / host (if given)
Database description (what the collection covers, including years and record type, based only on the provided text)
Credit line or original record creator (e.g., “National Archives and Records Administration [NARA], microfilm publication ___,” if stated)
Database‑level URL (home page or search page for this census collection)
Notes about coverage or limitations (e.g., missing counties, index only), if stated
Citation (household or person-level):
Person(s) of interest (focus person’s name and role in household)
Jurisdiction (state, county, town or township as given)
Enumeration details (e.g., enumeration district, ward, city, etc., if given)
Page and location information (page, sheet, line, dwelling, family numbers, as provided)
Schedule type (e.g., population schedule)
Event date or census date (as stated in the collection or text)
Record identifier(s) (e.g., NARA microfilm publication and roll number, image number, digital film number, or other site‑specific ID)
Access type (image, index, or both)
Access date (e.g., “22 March 2026,” if given, otherwise “[not stated]”)
Direct record URL (if any)
Notes about legibility, indexing errors, or variant spellings, if mentioned in the text
Output format (use these exact headings and keep this order):
Master source – U.S. census (online images)
Source name:
Census year:
Country:
State or territory:
Database / collection title:
Website title:
Publisher / host:
Database description:
Credit line / original creator:
Database URL:
Database notes:
Citation – household / person
Persons of interest:
Jurisdiction:
Enumeration details:
Page / sheet / line / dwelling / family:
Schedule type:
Census date / event date:
Record identifiers (film / roll / image / DGS / etc.):
Access type:
Access date:
Record URL:
Item notes:
Here is the imported census source / citation text to clean and analyze:
<<<PASTE IMPORTED CENSUS SOURCE OR CITATION TEXT HERE>>>
