Difference between revisions of "Residence and census"

From Gramps
Jump to: navigation, search
m (More informations: spelling)
m (How or where could we set address on event ?)
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
[[Category:Documentation]][[Category:Tutorials]]
 
[[Category:Documentation]][[Category:Tutorials]]
{{languages|Residence and census}}
+
{{languages}}
  
  
Line 11: Line 11:
  
 
  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
+
  CENS {CENSUS} The event of the periodic count of the population for a designated
                        national orstate Census.
+
                        locality, such as a national orstate Census.
  TYPE {TYPE}  A further qualification to the meaning of the associated superior tag. The value does not  
+
  TYPE {TYPE}  A further qualification to the meaning of the associated superior tag.
                        have anycomputer processing reliability. It is more in the form of a short one or two word
+
                        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.
 
                         note that should be displayed any time the associated data is displayed.
  
Line 20: Line 21:
  
 
=== Multiples places ===
 
=== Multiples places ===
There is a lot of solutions :
+
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 informations for genealogical searchs !
+
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. (see [[Why_residence_event_and_not_Address%3F]])
+
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)
  
Line 48: Line 49:
 
|}
 
|}
  
I agree, we could use "(event type) of person's name" on both event type (residence and census), maybe with the "header of family" as person's name on census event.  
+
On description we could use "the "header of family" as person's name on census event.
  
 
=== To share data ===
 
=== To share data ===
  
* with Gramps XML format (to Gramps), there is no problem, descriptions on event are safe.
+
* Gramps XML format (from Gramps to Gramps): there is no problem, descriptions on event are safe.
* but if the recipient's program ignores TYPE attribut (GEDCOM), then he could lose descriptions on event ...
+
* Gedcom: if the recipient's program ignores TYPE attribut (GEDCOM), then he could lose descriptions on event ...
  
 
== More information ==
 
== More information ==

Revision as of 09:18, 10 October 2010


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 ?

Personaly, 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.

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 information