|
Revision as of 15:22, 11 September 2022 (edit) DataAnalyst (Talk | contribs)
← Previous diff |
Revision as of 15:22, 11 September 2022 (edit) DataAnalyst (Talk | contribs)
Next diff → |
Line 1: |
Line 1: |
- | Enter dates in '''d mmm yyyy''' format - case doesn't matter. WeRelate automatically transforms any date it can interpret into '''d Mmm yyyy''' format (e.g., 4 Sep 1753). It supports standard GEDCOM [[Help:Conventions/Date#Modifiers|modifiers]] (Bef, Aft, Bet/and, From/to, Cal, Abt, Est), which it automatically transforms to mixed case. Ambiguous numeric dates (e.g., 9/3/1876) aren't allowed. WeRelate supports dual dating - if you are entering dates prior to 1752 and aren't familiar with dual dating ('''d Mmm yyyy/yy'''), please read [[Help:Conventions/Date#Month number and dual dating|Month number and dual dating]].<br> | + | Enter dates in '''d mmm yyyy''' format - case doesn't matter. WeRelate automatically transforms any date it can interpret into '''d Mmm yyyy''' format (e.g., 4 Sep 1753). It supports standard GEDCOM [[Help:Conventions/Date#Modifiers|modifiers]] (Bef, Aft, Bet/and, From/to, Cal, Abt, Est), which it automatically transforms to mixed case. Ambiguous numeric dates (e.g., 9/3/1876) aren't allowed. WeRelate supports dual dating - if you are entering dates prior to 1752 and aren't familiar with dual dating ('''d Mmm yyyy/yy'''), please read [[Help:Conventions/Date#Month number and dual dating|Month number and dual dating]].<br><br> |
| | | |
| Proxy dates (e.g., christening date as proxy for birth date, or probate date as proxy for death date) should '''not''' be entered in the field that they are a proxy for, but should be entered as their own fact. When a christening or burial date is used as a proxy, do '''not''' enter a birth or death date that can be derived from the proxy (e.g., Bef ''christening date''). | | Proxy dates (e.g., christening date as proxy for birth date, or probate date as proxy for death date) should '''not''' be entered in the field that they are a proxy for, but should be entered as their own fact. When a christening or burial date is used as a proxy, do '''not''' enter a birth or death date that can be derived from the proxy (e.g., Bef ''christening date''). |
| | | |
| Source citations should give the date supported by the source in case the date in the date field is changed. If a non-trivial conversion is required, the source citation should include both the date as expressed in the source and the converted date (e.g., '''6 (6) 66 [6 Aug 1666]'''). | | Source citations should give the date supported by the source in case the date in the date field is changed. If a non-trivial conversion is required, the source citation should include both the date as expressed in the source and the converted date (e.g., '''6 (6) 66 [6 Aug 1666]'''). |
Revision as of 15:22, 11 September 2022
Enter dates in d mmm yyyy format - case doesn't matter. WeRelate automatically transforms any date it can interpret into d Mmm yyyy format (e.g., 4 Sep 1753). It supports standard GEDCOM modifiers (Bef, Aft, Bet/and, From/to, Cal, Abt, Est), which it automatically transforms to mixed case. Ambiguous numeric dates (e.g., 9/3/1876) aren't allowed. WeRelate supports dual dating - if you are entering dates prior to 1752 and aren't familiar with dual dating (d Mmm yyyy/yy), please read Month number and dual dating.
Proxy dates (e.g., christening date as proxy for birth date, or probate date as proxy for death date) should not be entered in the field that they are a proxy for, but should be entered as their own fact. When a christening or burial date is used as a proxy, do not enter a birth or death date that can be derived from the proxy (e.g., Bef christening date).
Source citations should give the date supported by the source in case the date in the date field is changed. If a non-trivial conversion is required, the source citation should include both the date as expressed in the source and the converted date (e.g., 6 (6) 66 [6 Aug 1666]).
|
|