Difference between revisions of "Residence and census"
m |
CallMeDave (talk | contribs) |
||
(12 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
− | |||
{{languages|Residence and census}} | {{languages|Residence and census}} | ||
− | |||
− | |||
==Introduction== | ==Introduction== | ||
Line 11: | Line 8: | ||
RESI {RESIDENCE} The act of dwelling at an address for a period of time. | RESI {RESIDENCE} The act of dwelling at an address for a period of time. | ||
− | CENS {CENSUS} The event of the periodic count of the population for a designated locality, such as a national orstate Census. | + | CENS {CENSUS} The event of the periodic count of the population for a designated |
− | TYPE {TYPE} A further qualification to the meaning of the associated superior tag. The value does not have anycomputer processing reliability. It is more in the form of a short one or two word note that should be displayed any time the associated data is displayed. | + | locality, such as a national orstate Census. |
+ | TYPE {TYPE} A further qualification to the meaning of the associated superior tag. | ||
+ | The value does not have anycomputer processing reliability. | ||
+ | It is more in the form of a short one or two word | ||
+ | note that should be displayed any time the associated data is displayed. | ||
== Place and Address == | == Place and Address == | ||
=== Multiples places === | === Multiples places === | ||
− | There | + | There are many solutions : |
* GEDCOM 5.5 allows a sub-division on place title separated by commas. | * GEDCOM 5.5 allows a sub-division on place title separated by commas. | ||
But using a specific address as place title (or place attribute) might generate a lot of place objects on the same city or same district (no shared place object). | But using a specific address as place title (or place attribute) might generate a lot of place objects on the same city or same district (no shared place object). | ||
* Gramps provides an Address tab on person editor. | * Gramps provides an Address tab on person editor. | ||
− | But maybe an other GEDCOM issue, which could hide some useful | + | But maybe an other GEDCOM issue, which could hide some useful information for genealogical searches! |
− | * The most effective emplacement for setting address seems to be the event editor | + | * The most effective emplacement for setting address seems to be the event editor! |
− | Event objects are used on reports and displayed on views/tabs/dialogs. | + | Event objects are used on reports and displayed on views/tabs/dialogs. (see [[Why residence event and not Address%3F]]) |
Most places deal with events (see Place Report) | Most places deal with events (see Place Report) | ||
=== How or where could we set address on event ? === | === How or where could we set address on event ? === | ||
− | + | Personally, I find the '''event description''' a good choice : | |
{|{{prettytable}} | {|{{prettytable}} | ||
Line 45: | Line 46: | ||
|} | |} | ||
− | + | On description we could use "the "header of family" as person's name on census event. | |
=== To share data === | === To share data === | ||
− | * | + | * Gramps XML format (from Gramps to Gramps): there is no problem, descriptions on event are safe. |
− | * | + | * Gedcom: if the recipient's program ignores TYPE attribut (GEDCOM), then he could lose descriptions on event ... |
− | == More | + | == More information == |
*[[Why_residence_event_and_not_Address%3F|why event rather than address]] ? | *[[Why_residence_event_and_not_Address%3F|why event rather than address]] ? | ||
− | *[[ | + | *[[Recording UK Census data]] |
− | *[[ | + | *[[Recording FR Census data]] |
+ | |||
+ | |||
+ | [[Category:Documentation]] | ||
+ | [[Category:Tutorials]] |
Latest revision as of 04:08, 19 March 2022
Contents
Introduction
Events
Residence and census are on GEDCOM 5.5 specifications :
RESI {RESIDENCE} The act of dwelling at an address for a period of time. CENS {CENSUS} The event of the periodic count of the population for a designated locality, such as a national orstate Census. TYPE {TYPE} A further qualification to the meaning of the associated superior tag. The value does not have anycomputer processing reliability. It is more in the form of a short one or two word note that should be displayed any time the associated data is displayed.
Place and Address
Multiples places
There are many solutions :
- GEDCOM 5.5 allows a sub-division on place title separated by commas.
But using a specific address as place title (or place attribute) might generate a lot of place objects on the same city or same district (no shared place object).
- Gramps provides an Address tab on person editor.
But maybe an other GEDCOM issue, which could hide some useful information for genealogical searches!
- The most effective emplacement for setting address seems to be the event editor!
Event objects are used on reports and displayed on views/tabs/dialogs. (see Why residence event and not Address?) Most places deal with events (see Place Report)
How or where could we set address on event ?
Personally, I find the event description a good choice :
Residence | Census | |
---|---|---|
Event | Individual or family | Shared (People and Family) |
Source | Certificate or a card | Census (Place and date) |
Place | no sub-division for address (city, code, county, state, country) | no sub-division for address (city, code, county, state, country) |
Event description | Residence of Surname, Given name - address (number street) | Address (number street) |
On description we could use "the "header of family" as person's name on census event.
- Gramps XML format (from Gramps to Gramps): there is no problem, descriptions on event are safe.
- Gedcom: if the recipient's program ignores TYPE attribut (GEDCOM), then he could lose descriptions on event ...