-
Notifications
You must be signed in to change notification settings - Fork 21
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.
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
FAMC.PEDI.DATE #256
Comments
Discussed in steering committee We know of a practical need for this, including implementations today doing this as an extension. Adding |
Currently FAMC.PEDI is (1) a date for the whole
or (2) multiple
not (3) a single dated-
but I'd be interested in your take @dhesmer (as well as anyone else implementing this as an extension currently) |
Lets say a child was eventually adopted by their foster parents. So for some period of time This is a little similar to the case we dealt with in the remarriage1.ged and remarriage2.ged test files where we permit storing as either one or two families. So I think this argues for Luther's option (2) being at least permitted, even if multiple ways to represent are permitted. |
As Dave Thaler noted that multiple PEDI relationships can occur, I prefer option 2. |
Also makes PEDI {0:M} not {0:1}, which could have use (e.g. when a child was both adopted by and fostered to the same family) even without knownig dates.
Resolve #256 by adding PEDI.DATE
PR #274 fixed this in the next-minor branch |
There are situations where individuals are foster children in different families at different times. In order to also document this in GEDCOM, a time stamp is required. Currently, this is not provided by the FAMC.PEDI structure.
+1 FAMC @XREF:FAM@
+2 PEDI
+3 PHRASE
To this current structure a
+3 DATE
should be added.
Currently the PHRASE could be used by a "FROM TO" Text.
Or ist a "+3 _DATE FROM ... TO ..." a better solution?
The text was updated successfully, but these errors were encountered: