Difference between revisions of "namesake"

From GeneWeb
Jump to: navigation, search
m
(expliciting index)
 
(6 intermediate revisions by one other user not shown)
Line 1: Line 1:
{{DISPLAYTITLE:Managing namesake with occurence numbers}}
+
{{DISPLAYTITLE:Managing namesake with occurrence numbers}}
 
{{languages|namesake}}
 
{{languages|namesake}}
 +
In a GeneWeb base, '''a person is uniquely identified through its first name, its last name and an occurrence number'''.
  
In a GeneWeb base, a person is uniquely identified through its first-name, its last-name and an '''occurence''' number which guarantees uniqueness in case of homonyms.
+
The occurrence number guarantees uniqueness in case of homonyms. There is no constraint when choosing the occurrence number for a new homonym. This number is not displayed on the personal data result page, but is visible in the URL window of your browser (and on some templates). If there are no homonyms, “0” is assumed and there is no need to enter it.  
  
This set, called the index of this person, may be replaced by a more compact unique (but non stable) numerical value. Its explicit form is used for:
+
This occurrence number is totally disconnected from the first-name number found in Louis IVX for instance, but it can be helpful to choose the same number.  
* [[update|Update forms]].
+
* [[search|Search of a person]]: {{c|first-name.occurence last-name}}.
+
* [[wikitext#Internal links|Internal links]]: {{c|<nowiki>[[first-name/last-name/occurence/displayed text]]</nowiki>}}.
+
* Reference image (portraits): {{c|first-name.occurence.last-name.jpg}}.
+
  
Note that except in the data capture situation, GeneWeb ignores accented characters. This forces you to choose a different occurence number for two individuals whose names differ only through an accented letter. GeneWeb assumes that European ISO-8859-1 coding is used. Using another coding should not trigger an error but yields strange results.
+
When importing from GEDCOM files, the occurrence assignment is done automatically.
  
There is no constraint when choosing the occurence number for a new homonym. This number is not displayed on the personal data result page, but is visible in the URL window of your browser (and on some templates). If there are no homonyms, “0” is assumed and there is no need to enter it.  
+
When [[merge|merging multiple bases]], the gwc command allows some control by offsetting automatically potentially conflicting numbers (assumes that two identical persons from two different source files should not considered to be the same. Possible merge should happen later under your control). A second possibility is to ask gwc to shift all numbers of a source file by some value.
  
This occurence number is totally disconnected from the first-name number found in Louis IVX for instance, but it can be helpful to choose the same number.  
+
The set first name/last name/occurrence number, called the index of this person (appearing as %index; in templates code), may be replaced by a more compact unique (but non stable) numerical value ({{c|1=oc=…}}). Its explicit form is used for:
 +
* [[update|Update forms]].
 +
* [[search|Search of a person]]: {{c|first-name.occurrence last-name}}.
 +
* [[wikitext#Internal links|Internal links]]: {{c|<nowiki>[[first-name/last-name/occurrence/displayed text]]</nowiki>}}.
 +
* Reference [[Update#Send an image|image]]: {{c|first-name.occurrence.last-name.jpg}}.
  
When importing from GEDCOM files, the occurence assignment is done automatically.
+
Note that except in the data capture situation, GeneWeb ignores accented characters. This forces you to choose a different occurrence number for two individuals whose names differ only through an accented letter. GeneWeb assumes that European ISO-8859-1 coding is used. Using another coding should not trigger an error but yields strange results.
 
+
When [[merge|merging multiple bases]], the gwc command allows some control by offsetting automatically potentially conflicting numbers (assumes that two identical persons from two different source files should not considered to be the same. Possible merge should happen later under your control). A second possibility is to ask gwc to shift all numbers of a source file by some value.
+
  
 
GeneWeb produces on occasion error messages describing two possible situations:
 
GeneWeb produces on occasion error messages describing two possible situations:
* “Person already exists” at person creation time. You either should link to that person rather than create it, or select a new occurence number.
+
* “Person already exists” at person creation time. You either should link to that person rather than create it, or select a new occurrence number.
* “Unknown perso”, situation that may happen if you want to link to an existing person but omit or incorrectly specify the occurence number.  
+
* “Unknown perso”, situation that may happen if you want to link to an existing person but omit or incorrectly specify the occurrence number.  
 +
 
 +
Be careful when entering occurrence numbers as you could link or [[fusion|merge a person]] with the wrong one. GeneWeb cannot detect these errors.
 +
 
 +
{{manual}}
  
Be careful when entering occurence numbers as you could link or [[fusion|merge a person]] with the wrong one. GeneWeb cannot detect these errors.
+
[[Category:Manual]]

Latest revision as of 14:26, 8 June 2016

150px-Geographylogo svg.png Language: English • français

In a GeneWeb base, a person is uniquely identified through its first name, its last name and an occurrence number.

The occurrence number guarantees uniqueness in case of homonyms. There is no constraint when choosing the occurrence number for a new homonym. This number is not displayed on the personal data result page, but is visible in the URL window of your browser (and on some templates). If there are no homonyms, “0” is assumed and there is no need to enter it.

This occurrence number is totally disconnected from the first-name number found in Louis IVX for instance, but it can be helpful to choose the same number.

When importing from GEDCOM files, the occurrence assignment is done automatically.

When merging multiple bases, the gwc command allows some control by offsetting automatically potentially conflicting numbers (assumes that two identical persons from two different source files should not considered to be the same. Possible merge should happen later under your control). A second possibility is to ask gwc to shift all numbers of a source file by some value.

The set first name/last name/occurrence number, called the index of this person (appearing as %index; in templates code), may be replaced by a more compact unique (but non stable) numerical value (oc=…). Its explicit form is used for:

Note that except in the data capture situation, GeneWeb ignores accented characters. This forces you to choose a different occurrence number for two individuals whose names differ only through an accented letter. GeneWeb assumes that European ISO-8859-1 coding is used. Using another coding should not trigger an error but yields strange results.

GeneWeb produces on occasion error messages describing two possible situations:

  • “Person already exists” at person creation time. You either should link to that person rather than create it, or select a new occurrence number.
  • “Unknown perso”, situation that may happen if you want to link to an existing person but omit or incorrectly specify the occurrence number.

Be careful when entering occurrence numbers as you could link or merge a person with the wrong one. GeneWeb cannot detect these errors.


GeneWeb Manual

Rembrandt Old Man Reading a Book.jpg

Use and manage genealogical databases

Technical annex