Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Source of a child-parents relationship #93

Merged
merged 3 commits into from
Sep 21, 2023
Merged

Source of a child-parents relationship #93

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
569b7e0
Source of a child-parents relationship
dthaler Sep 21, 2023
703a466
Update _pages/techfaqs.md
tychonievich Sep 21, 2023
c6e958d
Update _pages/techfaqs.md
tychonievich Sep 21, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions _pages/techfaqs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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?
tychonievich marked this conversation as resolved.
Show resolved Hide resolved

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.

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:

```
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`:
Expand Down