From 569b7e0861ece6b49761fcbe8c37030cb7c9a99d Mon Sep 17 00:00:00 2001 From: Dave Thaler Date: Thu, 21 Sep 2023 11:59:38 -0700 Subject: [PATCH 1/3] Source of a child-parents relationship Per discussion in https://github.com/FamilySearch/GEDCOM/issues/346 Signed-off-by: Dave Thaler --- _pages/techfaqs.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/_pages/techfaqs.md b/_pages/techfaqs.md index f6e2d60..9722eb1 100644 --- a/_pages/techfaqs.md +++ b/_pages/techfaqs.md @@ -95,6 +95,23 @@ At present, the best available tool is `INDI.FAMC.PEDI`, one for each family: Because the nature of `BIRTH` is unclear (is it about the biological progenitors of the child or the social family unit into which it is born?) and a topic some researchers have strong feelings about, either or both of the above may be recorded `PEDI OTHER` instead of `PEDI BIRTH` by some researchers. +# How do I provide a source citaton for a parent-child relationship? + +Neither the `FAMC` structure of an individual record nor the `CHIL` structure of a family record supports +having a `SOUR` citation as a substructure. Today applications often put the `SOUR` directly under the +individual record or the family record, where it lacks specificity in terms of which family or individual +it applies to. + +To maintain specificity, the best place to put the `SOUR` citation today is under an `INDI.BIRT` +as in the following example: + +``` +0 @I1@ INDI +1 BIRT +2 SOUR @S2@ +2 FAMC @F3@ +``` + # How do I mark a parent-child relationship as confidential? The standard `RESN` tag is used to mark data confidential but it is not a substructure under the `FAM.FAMC` or `FAM.CHIL` tags. You can implement a custom extension tag, perhaps `_RESN`, and add a `SCHMA` entry to indicate the extension has the same meaning as `RESN`: From 703a466f0725e531ccccc4399c9de9178be841eb Mon Sep 17 00:00:00 2001 From: Luther Tychonievich Date: Thu, 21 Sep 2023 14:16:41 -0500 Subject: [PATCH 2/3] Update _pages/techfaqs.md --- _pages/techfaqs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_pages/techfaqs.md b/_pages/techfaqs.md index 9722eb1..a55c90f 100644 --- a/_pages/techfaqs.md +++ b/_pages/techfaqs.md @@ -102,7 +102,7 @@ having a `SOUR` citation as a substructure. Today applications often put the `S individual record or the family record, where it lacks specificity in terms of which family or individual it applies to. -To maintain specificity, the best place to put the `SOUR` citation today is under an `INDI.BIRT` +If the source applies to a birth or adoption, specificity can be maintained by placing the `SOUR` citation under an `INDI.BIRT` or `INDI.ADOP`, as in the following example: ``` From c6e958d033d83437e87a258c13754b19d620b466 Mon Sep 17 00:00:00 2001 From: Luther Tychonievich Date: Thu, 21 Sep 2023 14:16:59 -0500 Subject: [PATCH 3/3] Update _pages/techfaqs.md --- _pages/techfaqs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_pages/techfaqs.md b/_pages/techfaqs.md index a55c90f..dad442b 100644 --- a/_pages/techfaqs.md +++ b/_pages/techfaqs.md @@ -95,7 +95,7 @@ At present, the best available tool is `INDI.FAMC.PEDI`, one for each family: Because the nature of `BIRTH` is unclear (is it about the biological progenitors of the child or the social family unit into which it is born?) and a topic some researchers have strong feelings about, either or both of the above may be recorded `PEDI OTHER` instead of `PEDI BIRTH` by some researchers. -# How do I provide a source citaton for a parent-child relationship? +# How do I provide a source citation for a parent-child relationship? Neither the `FAMC` structure of an individual record nor the `CHIL` structure of a family record supports having a `SOUR` citation as a substructure. Today applications often put the `SOUR` directly under the