Skip to content

Commit

Permalink
Merge pull request #373 from FamilySearch/source-stewardship
Browse files Browse the repository at this point in the history
Source stewardship support
  • Loading branch information
dthaler authored Nov 16, 2023
2 parents 4007aec + 82f9ad4 commit 62d5b9f
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions specification/gedcom-3-structures-1-organization.md
Original file line number Diff line number Diff line change
Expand Up @@ -1229,6 +1229,7 @@ n REPO @<XREF:REPO>@ {1:1} g7:REPO
+1 CALN <Special> {0:M} g7:CALN
+2 MEDI <Enum> {0:1} g7:MEDI
+3 PHRASE <Text> {0:1} g7:PHRASE
+1 DATE <DateValue> {0:1} g7:DATE
```

This structure is used within a source record to point to a name and address record of the holder of the source document.
Expand All @@ -1237,3 +1238,7 @@ Formal and informal repository name and addresses are stored in the
More formal repositories, such as the Family History Library, should show a call number of the source at that repository.
The call number of that source should be recorded using a `CALN` substructure.

A `DATE` substructure can be used to denote the date when the source was known to be held by the
specific holder. For example, if a Family Bible was passed from one person to another over time, a
`SOURCE_REPOSITORY_CITATION` with a `DATE` substructure can be used to track the provenance as it was handed down.

0 comments on commit 62d5b9f

Please sign in to comment.