ZongMai Genealogy Compilation Guide
Phone numbers, addresses, sensitive experiences, and unpublished materials of living relatives should be protected through permissions and review mechanisms.
Genealogy Compilation in Practice · Updated 2026-09-22
An internal family proof, printed copies shared as gifts, and public pages on the internet have different audiences. Before collecting materials, explain how they will be used and confirm item by item which content may be included in each version. Do not assume that because a relative is willing to provide materials in a family group, they also consent to making them public in search engines.
When compiling a person's life story, it is usually unnecessary to publish ID numbers, exact addresses, telephone numbers, or account information. Retain the names, relationships, and verified experiences necessary for the article's purpose; details that do not affect the narrative can be summarized. Be especially cautious with information about minors, and first confirm how it will be used with their guardians.
ID-document photos, envelopes, school materials, and recordings may contain information not mentioned in the main text. Before publishing, enlarge and inspect all four corners and the backs of images and review the attachments; create copies suitable for public release and store the originals separately. Do not merely cover text on the page while still allowing readers to download the unedited original files.
The index can include columns for “provider,” “permitted use,” “whether public release is allowed,” “confirmation date,” and “change history.” For group photos and interviews involving multiple people, check each relevant person's views separately. This article offers suggestions for an editorial workflow and does not replace professional judgment on specific disputes; materials about which you are uncertain can first be saved as internal drafts pending review.
Explain to family members how to request corrections or adjustments to the scope of public release, and record when the request was received, who handled it, and the outcome. After making changes to a public page, also check its attachments and historical download links; keep internal revision records to prevent an old version from being republished the next time the page is generated.
