Here’s a concrete, genealogy‑oriented pattern you can lift straight into your own Zotero libraries, based on current Zotero guidance plus the “Zotero, Genealogy, and Citations” forum blueprint. I’ll focus on one coherent model rather than lots of variants so it’s easy to teach and reuse.zotero+5
Collection structure examples
Think of collections as your “filing cabinets” by person and project, not as the place you encode research status or evidence type.zotero+2
Top level in a dedicated genealogy library (group or personal):[forums.zotero]
-
Genealogy Projects / Case Studies
-
Reference Library (methodology, locality guides, maps, background reading)
-
DNA Projects (if you prefer to separate them)
Inside “Genealogy Projects / Case Studies”, create one collection per individual or tightly scoped case:[forums.zotero]
-
Finnie, John (1780–1855) – Kilmarnock
-
Ross, Margaret (c.1820–1890) – Ayrshire
-
Clark, William H. (1872–1939) – Okmulgee County
Within each individual’s collection, copy a standard set of life‑event and analysis subcollections (these are directly adapted from the forum template):[forums.zotero]
-
00 Research Control
-
01 Identity & Hypothesis
-
02 Birth & Baptism
-
03 Marriage(s)
-
04 Death & Burial
-
05 Occupation & Residence
-
06 Children
-
07 Associates & FAN Club
-
08 DNA & Genetic Evidence
-
09 Conflicting / Excluded Evidence
-
10 Correspondence & Notes
Two operational rules from that thread are worth keeping intact:[forums.zotero]
-
All documents live only in the lowest relevant subcollection (no scattering the same census image across three places).
-
Higher‑level collections (family line, “Genealogy Projects / Case Studies” itself) hold structure only, not items.
Standard tag sets you can reuse
Tags carry the analytical weight: status, evidence type, GPS stage, line, and anything search‑driven you want to slice across people.zotero+3
Status tags (workflow):[forums.zotero]
-
status: unreviewed
-
status: reviewed
-
status: conflict
-
status: resolved
-
status: to‑do
-
status: negative
Evidence type tags (what is this thing?):[forums.zotero]
-
type: birth
-
type: baptism
-
type: marriage
-
type: death
-
type: burial
-
type: residence
-
type: occupation
-
type: DNA
-
type: FAN
-
type: correspondence
-
type: primary
-
type: secondary
GPS / analytical phase tags (where does this item sit in your proof process):[forums.zotero]
-
gps: collect
-
gps: analyse
-
gps: conflict
-
gps: resolve
-
gps: proof
Line or project tags (cross‑person views):[forums.zotero]
-
line: Finnie
-
line: Ross
-
line: Clark
-
project: Okmulgee oil boom study
To keep the tag selector usable, the forums and Zotero docs both suggest turning off automatic import of web‑tags and intentionally designing a small, reused set like this.youtube+1[zotero]
How collections and tags work together
The forums consistently recommend using collections for coarse project structure and tags for everything that needs to cut across projects or individuals. In a genealogy context, that gives you patterns like:zotero+4
-
Store a 1900 census page for John Finnie in “Finnie, John (1780–1855) – Kilmarnock → 05 Occupation & Residence”.[forums.zotero]
-
Tag it: status: reviewed, type: residence, type: occupation, type: primary, line: Finnie, gps: analyse.[forums.zotero]
-
Later, retrieve “all residence evidence for the Finnie line” by filtering on line: Finnie + type: residence, regardless of which person’s collection it lives in.zotero+1
Saved searches then become your cross‑section tools, which one forum post explicitly highlights as the payoff for a tag‑heavy strategy.zotero+3
Sample saved searches (expressed in plain language):[forums.zotero]
-
“Ready for analysis”: gps: collect AND status: reviewed
-
“Conflicts not yet resolved”: gps: conflict AND NOT gps: resolve
-
“Completed proofs”: gps: proof
Small table you can paste into a briefing
Would it be useful if I next drafted 2–3 concrete worked examples (e.g., a full set of records for one census household) showing exactly how you’d name, file, and tag each item step‑by‑step?
No comments:
Post a Comment