PGVWiki - User contributions [en]

Build a New Menu

2008-12-06T14:11:01Z

Elliott1961:

Genealogy is what is in your database; the names, facts, and events. Of course, you can put stories in notes, but sometimes you wish to have separate pages where you can, for example, detail a family history, present images with commentary, or have a links page. With this tutorial, you will learn how to modify PhpGedView to show a custom menu linking to custom pages with the standard PhpGedView header and footer.

== Add a new Menu ==
Before you make any changes, please [[How_To:Customize_Themes|save]] the theme "Cloudy" and work only on a renamed copy of it.

You will find the relevant PHP-code in the file "'''header.html'''". 
Because every theme has its own menu-system, we will show you the essential changes as an example for the theme "'''Cloudy'''". 
In my case, I have set the variable for User-may-change-Themes to "no" and Standard-Theme to "Cloudy". 
The "header.html" for "Cloudy" you will find in the following path:

/phpGedView/themes/cloudy/header.html

Open the file with an html-editor or with a simple text-editor. 
Search for the first entry like:

$my_temp_menu= array();

The following lines build the first menu-point in PGV, shown in the PGV-page by the "Home"-icon. 
All the stuff from this Home-menu (plus its submenus) is enclosed between "<nowiki><td></nowiki>" and "<nowiki></td></nowiki>" -tags. 
Every next "<nowiki><td></nowiki>...<nowiki></td></nowiki>" -block encloses such a menu-icon with the concerning submenus. 
A dozen menu-items are enclosed in a "<nowiki><table></nowiki>...<nowiki></table></nowiki>" -tag. 
The general '''menu-structure''' looks like this:

<pre>
<table>
<tr>
<td>
1. menu-item (with all submenu-items)
</td>
</tr>
<tr>
<td>
2. menu-item (with all submenu-items)
</td>
</tr>
</tr>
<td>
maybe your own new menu-item (with all submenu-items)
</td>
</tr>
<tr>
<td>
last menu-item (with all submenu-items)
</td>
</tr>
</table>
</pre>

The code for the '''menu''' and the '''submenus''' looks like this:


<td valign="middle" width="1" >
<?php
$menu = array();
$menu["label"] = "...............";
$menu["labelpos"] = "none";
$menu["icon"] = "...............";
$menu["class"] = "menuitem";
$menu["hoverclass"] = "menuitem_hover";
$menu["flyout"] = "down";
$menu["submenuclass"] = "submenu$ff";
$menu["items"] = array();

$submenu = array();
$submenu["label"] = "...............";
$submenu["labelpos"] = "right";
$submenu["icon"] = "...............";
$submenu["link"] = "...............";
$submenu["class"] = "submenuitem$ff";
$submenu["hoverclass"] = "submenuitem_hover$ff";

print_menu($menu);
?>
</td>


With "copy and paste" take this code above and put it between two <td>-blocks, where you would place your new menu-item, as shown in the general menu-structure above. 

Now we will learn how you can change the essental code-lines to do what you want to do. 

You have the '''$menu'''-block, which builds the upper-icon you will see on the PGV-page
and the '''$submenu'''-block, which builds the popup-menu with the submenu-entries on the PGV-page. 

You can copy this $submenu-block as many times as you need, there is one block for every submenu-entry. 

The print_menu-line prints the menu-item (including the submenu-items) to the PGV-page. 

Find an meaningful '''label''' for every menu and submenu-entry, for example "my Family" and "where they came from" and write it like this:

$menu["label"] = "my Family";

$submenu["label"] = "where they came from"; 

Design a '''new menu-icon''' with a drawing-program or you will find an existing one with Google. Store it with a new name for example "newmenuicon.gif" in the following path:

/phpGedView/themes/cloudy/images/newmenuicon.gif

and call it in the code like this:

$menu["icon"] = "themes/cloudy/images/newmenuicon.gif";

You can also just use the icon PhpGedView uses for the Welcome Page.

== Open an External Link ==

To open an external link in the '''same browser-window''':
<pre>
$submenu["link"] = "http://www.frappr.com";
</pre>
To open an external link in a '''new browser-window''':
<pre>
$submenu["link"] = "http://www.frappr.com\" target=\"_blank\"";
</pre>
To open an external link in a '''popup-window''':
<pre>
$submenu["link"] = "#\" onclick=\"window.open('http://www.frappr.com','','
left=50,top=50,width=600,height=320,resizable=1,scroll bars=1'); \"";
</pre>

left = distance of the windows from left sideborder 
top = distance of the windows from upper sideborder 
width = width of the windows 
height = height of the windows 
scrollbars = 1 with scrollbars 
scrollbars = 0 without scrollbars 

== Build a new HTML page ==
Write an HTML (or PHP) page in the usual manner and include all the stories about your family you want to show your users. Create a "pages" directory in your PhpGedView installation, and place the file here. For example, save it as http://www.mysite.com/phpgedview/pages/mypage.html.

== Display the HTML page ==
I am not a PHP developer and cannot vouch for the security of this method. Alternately, you can create a separate page containing all the surrounding code for each page you want to make.
Create a file named page.php in your PGV base installation directory, containing this text:

<?php
require("config.php");
print_header("PhpGedView Page"); ?>
include("pages/".$_GET["page"]);
print_footer();
?>

You can then display your pages by going to http://www.mysite.com/phpgedview/page.php?page=mypage.html. It will be shown with the standard PGV header and footer. If you want to format all your pages a certain way, like with a block similar to those on the Welcome Page, you can put the code around the include("pages/".$_GET["page"]); line, so you don't have to write it in every html file.

== Examples ==
PGV-Sites with new Menu and Stories around
* [http://www.lau-net.de/baerlocher/phpGedView Example from Markus (Theme "Cloudy")]
* [http://www.finison.com Example from Michael (Theme: slightly-modified Myst)]

CMS-Sites with PGV inside
(see also an [[How_to:Integrate_with_CMS|introduction]] of this)
* [http://www.thelewisfamily.id.au Example from Laurie (Joomla!)]
* [http://www.zeisberg-laudert.de Example from Bernd (Joomla!)]
* [http://www.colt49.com/familyhistory Example from Nigelo (HTML, Theme "Wooden")]
* [http://www.our-families.info Example from Nigelo (Joomla!)]

********** 
For Markus 
[[How To:Customize Themes|This is a link to How to customise themes]] 
[[How To:Customize Themes#Tutorials|This is a link to How to customise themes - Tutorials]] 
[[How To:Build a New Menu#Open a HTML-Text|This will take you to another sub heading item]] 
--[[User:Laurie|Laurie Lewis]] 17:34, 12 May 2006 (EST)

[[Category:How To]]


[[fr: Comment construire un nouveau menu]]

SOURCE CITATION

2008-11-01T20:08:56Z

Elliott1961:

A [[SOURCE CITATION]] is a reference to a [[SOURCE RECORD]] within another record type. A source record is an actual item which can be found within a library or other repository. A source citation references this source record, specifying the details of the citation like a chapter, page, or line.

SOURCE_CITATION: =
[
n SOUR @<[[XREF:SOUR]]>@ {1:1}
+1 PAGE <[[WHERE_WITHIN_SOURCE|WHERE_WITHIN_SOURCE]]> {0:1}
+1 EVEN <[[EVENT_TYPE_CITED_FROM|EVENT_TYPE_CITED_FROM]]> {0:1}
+2 ROLE <[[ROLE_IN_EVENT|ROLE_IN_EVENT]]> {0:1}
+1 DATA {0:1}
+2 DATE <[[ENTRY_RECORDING_DATE|ENTRY_RECORDING_DATE]]> {0:1}
+2 TEXT <[[TEXT_FROM_SOURCE|TEXT_FROM_SOURCE]]> {0:M}
+3 [ CONC | CONT ] <[[TEXT_FROM_SOURCE|TEXT_FROM_SOURCE]]> {0:M}
+1 QUAY <[[CERTAINTY_ASSESSMENT|CERTAINTY_ASSESSMENT]]> {0:1}
+1 <<[[MULTIMEDIA_LINK|MULTIMEDIA_LINK]]>> {0:M}
+1 <<[[NOTE_STRUCTURE|NOTE_STRUCTURE]]>> {0:M}

or on systems using embedded sources (not used in PGV)

n SOUR <[[SOURCE_DESCRIPTION|SOURCE_DESCRIPTION]]> {1:1}
+1 [ CONC | CONT ] <[[SOURCE_DESCRIPTION|SOURCE_DESCRIPTION]]> {0:M}
+1 TEXT <[[TEXT_FROM_SOURCE|TEXT_FROM_SOURCE]]> {0:M}
+2 [CONC | CONT ] <[[TEXT_FROM_SOURCE|TEXT_FROM_SOURCE]]> {0:M}
+1 <<[[NOTE_STRUCTURE|NOTE_STRUCTURE]]>> {0:M}
]

[[Category:GEDCOM]]
[[Category: Gedcom Structures]]


[[fr:CITATION D'UNE SOURCE]]

XREF:FAM

2008-10-30T09:45:01Z

Elliott1961:

An [[XREF:FAM]] is a pointer to, or an unique identifier of, a [[FAM RECORD|family record]], for example ''F123''. In Gedcom it always appears enclosed in @ symbols, e.g. ''@F123@''

XREF:FAM

[[Category:GEDCOM]]

[[fr: XREF:FAM]]

CHILD LINKAGE STATUS

2008-10-30T09:35:42Z

Elliott1961:

A status code on opinion of the status of a child to family link.

* challenged = Linking is suspect, but the linkage has been neither proven nor disproven.
* disproven = There has been a claim by some that this child belongs to this family, but the linkage has been disproven.
* proven = There has been a claim by some that this child does not belongs to this family, but the linkage has been proven.

[[Category:GEDCOM]]

[[fr: STATUT DU LIEN FILIAL]]

SPOUSE TO FAMILY LINK

2008-10-29T07:12:39Z

Elliott1961:

The Spouse to Family Link Structure links the person to a family in his/her role as spouse, using the FAMS = FAMily as Spouse tag. See also [[CHILD TO FAMILY LINK]]

SPOUSE_TO_FAMILY_LINK:=
n FAMS @<XREF:FAM>@ {1:1}
+1 <<[[NOTE_STRUCTURE]]>> {0:M}

[[Category:GEDCOM]]
[[Category: Gedcom Structures]]

[[fr: LIEN UNION]]

CHILD TO FAMILY LINK

2008-10-27T17:10:56Z

Elliott1961:

The Spouse to Family Link Structure links the person to a family in his/her role as child, using the FAMS = FAMily as Child tag. The child can be born in the family but also adopted, foster etc. - see [[PEDIGREE_LINKAGE_TYPE]]. See also [[SPOUSE TO FAMILY LINK]]

CHILD_TO_FAMILY_LINK:=
n FAMC @<[[XREF:FAM]]>@ {1:1}
+1 PEDI <[[PEDIGREE_LINKAGE_TYPE]]> {0:1}
+1 STAT <[[CHILD_LINKAGE_STATUS]]> {0:1}
+1 <<[[NOTE_STRUCTURE]]>> {0:M}

[[Category:GEDCOM]]
[[Category: Gedcom Structures]]

[[fr: LIEN PARENTAL]]

FAM RECORD

2008-10-26T16:27:35Z

Elliott1961:

The '''FAMily record''' is used to record marriages, common law marriages, and family unions caused by two people becoming the parents of a child. There can be no more than one HUSB/father and one WIFE/mother listed in each FAM_RECORD. If, for example, a man participated in more than one family union, then he would appear in more than one FAM_RECORD. The family record structure assumes that the HUSB/father is male and WIFE/mother is female. The preferred order of the CHILdren pointers within a FAMily structure is chronological by birth.

FAM_RECORD: =
n @<[[XREF:FAM]]>@ FAM {1:1}
+1 <<[[FAMILY_EVENT_STRUCTURE|FAMILY_EVENT_STRUCTURE]]>> {0:M}
+2 HUSB {0:1}
+3 AGE <[[AGE_AT_EVENT|AGE_AT_EVENT]]> {1:1}
+2 WIFE {0:1}
+3 AGE <[[AGE_AT_EVENT|AGE_AT_EVENT]]> {1:1}
+1 HUSB @<[[XREF:INDI]]>@ {0:1}
+1 WIFE @<[[XREF:INDI]]>@ {0:1}
+1 CHIL @<[[XREF:INDI]]>@ {0:M}
+1 NCHI <[[COUNT_OF_CHILDREN|COUNT_OF_CHILDREN]]> {0:1}
+1 SUBM @<[[XREF:SUBM]]>@ {0:M}
+1 <<[[LDS_SPOUSE_SEALING|LDS_SPOUSE_SEALING]]>> {0:M}
+1 REFN <[[USER_REFERENCE_NUMBER|USER_REFERENCE_NUMBER]]> {0:M}
+2 TYPE <[[USER_REFERENCE_TYPE|USER_REFERENCE_TYPE]]> {0:1}
+1 RIN <[[AUTOMATED_RECORD_ID|AUTOMATED_RECORD_ID]]> {0:1}
+1 <<[[CHANGE_DATE|CHANGE_DATE]]>> {0:1}
+1 <<[[NOTE_STRUCTURE|NOTE_STRUCTURE]]>> {0:M}
+1 <<[[SOURCE_CITATION|SOURCE_CITATION]]>> {0:M}
+1 <<[[MULTIMEDIA_LINK|MULTIMEDIA_LINK]]>> {0:M}

[[Category:GEDCOM]]
[[Category: Gedcom Structures]]

[[fr: ENREGISTREMENT FAMILLE]]

MULTIMEDIA RECORD

2008-10-26T16:09:44Z

Elliott1961:

The [[MULTIMEDIA_RECORD]] collects the details for a multimedia file or a collection of multimedia files.

The BLOB context of the multimedia record was removed in version 5.5.1. A reference to a multimedia file was added to the record structure. The file reference occurs one to many times so that multiple files can be grouped together, each pertaining to the same context. For example, if you wanted to associate a sound clip and a photo, you would reference each multimedia file and indicate the format using the FORM tag subordinate to each file reference.

MULTIMEDIA_RECORD:=
n @XREF:OBJE@ OBJE {1:1}
+1 FILE <[[MULTIMEDIA_FILE_REFN|MULTIMEDIA_FILE_REFN]]> {1:M}
+2 FORM <[[MULTIMEDIA_FORMAT|MULTIMEDIA_FORMAT]]> {1:1}
+3 TYPE <[[SOURCE_MEDIA_TYPE|SOURCE_MEDIA_TYPE]]> {0:1}
+2 TITL <[[DESCRIPTIVE_TITLE|DESCRIPTIVE_TITLE]]> {0:1}
+1 REFN <[[USER_REFERENCE_NUMBER|USER_REFERENCE_NUMBER]]> {0:M}
+2 TYPE <[[USER_REFERENCE_TYPE|USER_REFERENCE_TYPE]]> {0:1}
+1 RIN <[[AUTOMATED_RECORD_ID|AUTOMATED_RECORD_ID]]> {0:1}
+1 <<[[NOTE_STRUCTURE|NOTE_STRUCTURE]]>> {0:M}
+1 <<[[SOURCE_CITATION|SOURCE_CITATION]]>> {0:M}
+1 <<[[CHANGE_DATE|CHANGE_DATE]]>> {0:1}

[[Category:GEDCOM]]
[[Category: Gedcom Structures]]



[[fr:ENREGISTREMENT MULTIMEDIA]

MULTIMEDIA LINK

2008-10-25T11:36:37Z

Elliott1961:

The [[MULTIMEDIA LINK]] structure provides a link to a the top level [[MULTIMEDIA_RECORD]] within any other record or substructure. Note that all information is included in the Media Object, no details are added in the link itself.

MULTIMEDIA_LINK: =
n OBJE @<[[XREF:OBJE]]>@ {1:1}

The alternative (embedded) form is used in some systems, but not in PGV

n OBJE {1:1}
+1 FORM <[[MULTIMEDIA_FORMAT|MULTIMEDIA_FORMAT]]> {1:1}
+1 TITL <[[DESCRIPTIVE_TITLE]]> {0:1}
+1 FILE <[[MULTIMEDIA_FILE_REFERENCE]]> {1:1}

[[Category:GEDCOM]]
[[Category: Gedcom Structures]]



[[fr: LIEN MULTIMEDIA]]

XREF:SUBM

2008-10-20T19:45:24Z

Elliott1961:

An [[XREF:SUBM]] is a pointer to, or an unique identifier of, a [[SUBMITTER RECORD|submitter record]], for example ''U123''. In Gedcom it always appears enclosed in @ symbols, e.g. ''@U123@''

[[XREF:SUBM]]

[[Category:GEDCOM]]

[[fr: XREF:SUBM]]

SUBMITTER RECORD

2008-10-19T13:21:27Z

Elliott1961:

The [[SUBMITTER RECORD]] identifies an individual or organization that contributed information contained in the GEDCOM file.

SUBMITTER_RECORD:=
n @<[[XREF:SUBM]]>@ SUBM {1:1}
+1 NAME <[[SUBMITTER_NAME]]> {1:1}
+1 <<[[ADDRESS_STRUCTURE]]>> {0:1}
+1 <<[[MULTIMEDIA_LINK]]>> {0:M}
+1 LANG <[[LANGUAGE_PREFERENCE]]> {0:3}
+1 RFN <[[SUBMITTER_REGISTERED_RFN]]> {0:1}
+1 RIN <[[AUTOMATED_RECORD_ID]]> {0:1}
+1 <<[[NOTE_STRUCTURE]]>> {0:M}
+1 <<[[CHANGE_DATE]]>> {0:1}

[[Category:GEDCOM]]
[[Category: Gedcom Structures]]

[[fr: ENREGISTREMENT SOUMETTEUR]]

RECORD

2008-10-19T07:18:41Z

Elliott1961:

The [[RECORD]] structure is the most used section of the [[GEDCOM]] file because this is where all the genealogical information is recorded. There are 7 types of records, but PhpGedView does not support the [[NOTE_RECORD|Note Record]] nor the [[SUBMITTER_RECORD|Submitter Record]]. In addition to one Header and one Trailer the Gedcom file contains nothing but records. The structures within records describe the record content and can reference other records.

RECORD: =
[
n <<[[FAM_RECORD|FAM_RECORD]]>> {1:1}
|
n <<[[INDIVIDUAL_RECORD|INDIVIDUAL_RECORD]]>> {1:1}
|
n <<[[MULTIMEDIA_RECORD|MULTIMEDIA_RECORD]]>> {1:M}
|
n <<[[NOTE_RECORD|NOTE_RECORD]]>> {1:1}
|
n <<[[REPOSITORY_RECORD|REPOSITORY_RECORD]]>> {1:1}
|
n <<[[SOURCE_RECORD|SOURCE_RECORD]]>> {1:1}
|
n <<[[SUBMITTER_RECORD|SUBMITTER_RECORD]]>> {1:1}
]

''See also:''
[[Gedcom data structure]]

[[Category:GEDCOM]]
[[Category: Gedcom Structures]]

[[fr: RECORD]]

Category:Gedcom Structures

2008-10-18T20:34:41Z

Elliott1961:

GEDCOM Standard defines a number of structures used in different combinations, top level structures as well as substructures that can be embedded at different levels.

[[Category:GEDCOM]]

[[fr: Catégorie:Structure d'un Gedcom]]

SUBM

2008-10-18T20:27:19Z

Elliott1961:

{{glossary
| meaning = Submitter
| description = An individual or organization who contributes genealogical data to a file or transfers it to someone else.
}}

[[Category:GEDCOM]]

[[fr: SUBM]]

SUBN

2008-10-18T08:06:46Z

Elliott1961:

{{glossary
| meaning = Submission
| description = Pertains to a collection of data issued for processing.
}}

[[Category:GEDCOM]]

[[fr: SUBN]]

FAM

2008-10-18T07:50:37Z

Elliott1961:

{{glossary
| meaning = Family
| description = Identifies a legal, common law, or other customary relationship of man and woman and their children, if any, or a family created by virtue of the birth of a child to its biological father and mother.
}}

[[Category:GEDCOM]]
[[Category:GEDCOM tags]]

[[fr: FAM]]

INDI

2008-10-18T07:50:24Z

Elliott1961:

{{glossary
| meaning = Individual
| description = A person.
}}

[[Category:GEDCOM]]
[[Category:GEDCOM tags]]

[[fr: INDI]]

Gedcom data structure

2008-10-04T20:54:44Z

Elliott1961:

Although this topic appears rather technical, it is very often helpful in working with genealogy to visualize the basic data structure in the ''Lineage-Linked Gedcom Form'', which is the underlying structure in PGV. The data in Gedcom are confined to Records, which can have sub-elements enclosed in them. The top level records live an independent life, and are referenced in other records.

The best example is an Individual (INDI) record, which describes an individual. Each individual has only a single record, all data and references are saved within. The individual can then be shown as a mother in a family, a child in another, an adopted child in a third family, etc., and each time we deal with the same individual (and a single record). Similarly, Family is a top level record.

==Top level records in Gedcom==

; Individual ([[INDI]])
: Each person has its own unique record
;Family ([[FAM]])
: Family record: family consists of at least one parent, typically two, and can have children in different roles.
; Multimedia ([[OBJE]])
: Each time you add a photograph, document, voice recording or other multimedia file, you are creating a Multimedia Object. The object has a file reference, as well as other attributes like Title, Description, Source etc. The Media visible at different locations (by the person, family, source etc) are in fact references to this single object. You can add more references by editing the Media Object.
;Source ([[SOUR]])
:Source object contains a description of the source of genealogical data in Gedcom. A book, article, document, email etc. can be a source. While editing individual, family and other records, you always add Source Citation, quoting the Source record and possibly adding the details. Many citations can point to the same source.
;Repository ([[REPO]])
:Repository is a location where one or many sources are located. It can be an archive, library or your home. The repository record describes how to locate the source, would anybody need to reach it. Multiple sources can point to the same repository.

There are four other top level records: '''Note ([[NOTE]])''', '''Submission ([[SUBN]])''', '''Submitter([[SUBM]]) '''and '''Header ([[HEAD]])''', but they do not perform such universal role as those listed above. The Note can be cross-referenced, but in PGV an alternative form is used, embedded in lower level entity. The Submission and Sumbitter play a role only in the file Header to indicate the details in submitting the file to LDS, and are not used in PGV.

While adding the top level records one should always consider, whether the record already exists, and only a reference is needed. In many places an option is presented to either create a new top level record (Multimedia, Source, Repository etc.) or to provide a link to an existing one (with a search function to help). Similarly, an existing person can be linked to a new family (as parent or child) or to an event (as associate) with different roles.

==Lower level elements and structures==
All other information, dates, facts, addresses, events etc. are entered each time they are needed to describe or complement any of the top level records. In other words, while a Person or Source is unique and described only once in a Gedcom file, the same Location, Residence, School, Fact etc. will be repeated as many times as needed. This suggess some tediousness in entering the same data many times, but PGV has tools to let you search and select some of them (e.g. places) and to copy and paste others (e.g. events and facts).

==See also==
*[[:Category:Gedcom Structures|Gedcom Structures]]
*[[GEDCOM|Introduction to Gedcom]]
*[[RECORD|Gedcom record structure]]
*[[Edit raw GEDCOM record]]

[[Category:Users Guide]]
[[Category:PhpGedView]]

[[fr: Structure des données d'un fichier Gedcom]]

Setting a Restriction

2008-07-18T06:11:57Z

Elliott1961:

[[PGV]] has extensive privacy settings, which allow the administrator to set detailed rules on who can see which data, living and dead people, persons not related (or distant relations), and more. An administrator [[Privacy File|guide to privacy settings]] gives instructions on this topic. In addition, a privacy settings can be attached to each fact or event. This is especially important if the specific data is sensitive (like ID or Social Security numbers), or the user does not wish for the fact to be visible to all. Instead deleting the fact, one can set appropriate privacy restriction (Gedcom tag [[RESN]]) for this individual fact. Restriction works with the global privacy setting, which can further restrict (but not relax) the restriction. The settings are:
; None
: Everybody with editing privileges can edit information, everybody can see if global privacy settings allow it.
; Do not change
: Only administrators and Gedcom administrators can edit; no change to visibility.
; Privacy
: The information is visible only to the user himself, and to Administrator and Gedcom administrator, and is hidden from everybody else, regardless of their status. Only user (if allowed editing) and admins can edit the information.
; Confidential
: Only administrators can view/edit the information, it is hidden from all other users.

[[Category:Users Guide]]
[[Category:PhpGedView]]

[[fr: Etablir une restriction]]

Common Data Elements

2008-07-18T06:10:00Z

Elliott1961: Undo revision 11044 by Elliott1961 (Talk)

This article describes common data elements: fields and structures, that are encountered in creating most [[Facts and Events]] concerning an individual or family.

;Type ([[TYPE]])
:Type categorizes facts and events. It is mandatory while using generic FACT or EVEN tags, and useful in some other cases. In general Type is not structured, and what you put here depends on context, for example Ordination of a buddhist monk can be ''lay'' or ''priest'' type, and Marriage can be ''religious'' or ''civil'' type, etc. Some common types are pre-defined and presented as choices.

;Date ([[DATE]])
{{main|Dates}}
:Dates must be entered in English, even if displayed in other languages, for example ''12 Jan 1824''. The user interface provides a calendar helper and will attempt to guess common date formats, for example if you enter ''2/17/2003'' or ''17.2.2003'', it will be corectly transformed into 12 FEB 2003. The Date field accepts both points in time and intervals, as well as approximate dates. Read the [[Dates]] article for details.

;Time ([[TIME]])
:Time complements date when important, for example when describing the Birth event. Enter time as hh:mm:ss, for example ''14:24:15'', using 24 hour clock (military time in the US). You can skip seconds and/or minutes, if unknown.

;Place ([[PLACE]])
{{main|Place data}}
:The convention requires that places are entered with fulll details, including the city or village, county, state or other higher level division, and country. This convention not only helps identify the place on a map, but is also used by PGV for some useful things like providing a hierarchy of places, displaying locations on Google maps and more. Read about the places in a separate article on [[Place data|Place data]].

;Address ([[ADDR]])
: The Address sctructure is used wherever the address information is relevant, for example in describing place of birth, marriage, education, etc. Enter the address just like it would appear on a mailing label, using multiple lines. There is another, structured form of Address, with fields for City, State, Code etc, which will be displayed by PGV if found in Gedcom. Address is also part of a Residence (RESI) fact for individual and family; it is recomended that the Residence fact is used to note the personal/family address information. The Address structure has also tags to indicate phone, fax, www and email address. PGV is flexible in reading the data, and it will also display the address, phone, email etc. if attached to individual directly (not in Residence structure).

;Agency ([[AGNC]])
: Agency is used wherever an institution is mentioned in describing a fact ot event. It can be a school or university for an Education fact, the employer for Occupation fact, etc.

;Associate ([[ASSO]])
: Associate is a person performing a role in the described event. It can be a priest, witness, best man, godmother, friend, etc., and may be part of the family or not. Keeping with Gedcom structure, this person has her/his own record, and it is only mentioned as associate (with corresponding role) by the event. In order to be so referenced the person must already exist in the database. Adding an unlinked person comes handy here (you need Admin privileges to do it) if the Associate is not part of the family.

;Source Citation ([[SOUR]])
{{main|Proper use of sources}}
: If possible, you should always quote the source of the information. The Source Citation structure helps you find and existing Source record or create one, and add details for this citation, including citation details (page in the surce), relevant text and even a Media Object. For details see article on [[Proper use of sources]].

;Note ([[NOTE]])
: Can be attached to virtually anything - a place to add notes and comments related to the item in question (person, fact, object, etc.).

;Multimedia Object ([[OBJE]])
{{main| Adding / Editing Media}}
:Media enliven and illustrate your family tree. You can create a new Media Object or make a reference to an existing one. See [[Adding / Editing Media]] for details.

;Restriction ([[RESN]])
{{main|Setting a Restriction}}
: In addition to PGV global privacy settings, you can set restrictions on each event adn fact, preventing others from editing or seeing the event. See [[Setting a Restriction]] for details.

[[Category:Users Guide]]
[[Category:PhpGedView]]

[[fr:Informations couramment rencontrées]]

RESN

2008-07-18T06:06:05Z

Elliott1961:

{{glossary
| meaning = Restriction
| description = A processing indicator signifying access to information has been denied or otherwise restricted.
}}

[[Category:GEDCOM]]

[[fr: RESN]]

NOTE

2008-07-17T06:05:45Z

Elliott1961:

{{glossary
| meaning = Note
| description = Additional information provided by the submitter for understanding the enclosing data.
}}

[[Category:GEDCOM]]

[[fr: Note]]

ASSO

2008-07-07T05:37:53Z

Elliott1961:

{{glossary
| meaning = Associates
| description = An indicator to link friends, neighbors, relatives, or associates of an individual.
}}

[[Category:GEDCOM]]
[[Category:GEDCOM tags]]


[[fr:ASSO]]

TYPE

2008-07-06T19:31:09Z

Elliott1961:

{{glossary
| meaning = Type
| description = A further qualification to the meaning of the associated superior tag. The value does not have any computer 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. In PGV it is used to categorize some events, for example Marriage ([[MARR]]) types are:
:* Religious
:* Civil
:* Registered partnership
:* Unknown
}}

[[Category:GEDCOM]]


[[fr:TYPE]]

TIME

2008-07-06T19:30:54Z

Elliott1961:

{{glossary
| meaning = Time
| description = A time value in a 24-hour clock format, including hours, minutes, and optional seconds, separated by a colon (:). Fractions of seconds are shown in decimal notation.
}}

[[Category:GEDCOM]]


[[fr:TIME]]

ADDR

2008-07-06T19:30:37Z

Elliott1961:

{{glossary
| meaning = Address
| description = The contemporary place, usually required for postal purposes, of an individual, a submitter of information, a repository, a business, a school, or a company.
}}

[[Category:GEDCOM]]


[[fr:ADDR]]

Evaluating Evidence Article

2008-07-04T05:49:10Z

Elliott1961: /* The Genealogical Proof Standard: A Five-Step Process */

==Evaluating Evidence==

'''Barbara Krasner-Khait asks Elizabeth Shown Mills about the
best practices for high-quality research.
'''
In modern times, when genealogists can access an incredible amount of records through compiled family trees available on the web and on CD, how will you know that information you see will meet the quality standards of genealogical research? Have you taken steps in your own research to cite your sources? Have you made any leaps of faith without documenting how and why you drew your conclusion?

For more than 20 years, Elizabeth Shown Mills has been educating family historians on techniques for proper documentation. Her first article on evidence, entitled “How to Properly Document Your Research Notes”, appeared in the September/October 1979 issue of Everton’s Genealogical Helper. With her husband’s help, she worked out patterns for evaluating evidence, listing 13 guidelines for analyzing evidence and another 13 for documentation, published in Evidence! Citation and Analysis for Family Historian (Genealogical Publishing Co., 1997).

Says Mills, “If we don’t know where something came from, we don’t know its value. We have no way of knowing what to believe or how to evaluate it versus another piece of information.”

===Evidence Defined===
Evidence is the information we use to reach our conclusions. We start out with “raw” data, analyze it to see how close it comes to reality, how it relates to the problem, and how it relates to the person we’re researching. This process produces evidence — the best information we have that allows us to draw a certain set of conclusions, while screening others out. Tom Jones, Virginia-based professional genealogist and president of the Board of Certification for Genealogists, says, “Typically researchers start with a research question, for example, who was the mother of John Smith, or where was Jane Johnson born. They search for sources and evidence that might shed light on the question, evaluate the evidence and, if the findings meet the Genealogical Proof — come to a conclusion about the answer to the research question.”

===Tie Each Detail to a Source===
Each bit of information has to carry its own weight. To Mills, the most important criterion is the one she lists first in her “Guidelines for Documentation”: “Any statement of fact that is not common knowledge must carry its own individual statement of source.” She says, “Tiny little facts are crucial to our needs.”

Sources can be original or derivative. And it’s this latter group that can be especially problematic. If a derivative source contains an error, that error can be amplified each time the source is copied. Carefully check citations to determine how close the information is to the original source.

Information can be either primary or secondary. Primary information represents first-hand knowledge of the recorder or the informant. Secondary information is everything else. Let’s say you have an ancestor’s death record. This can be considered a primary source on the physician, because he provided the information himself. The death record is also a secondary source for information on the decedent’s parentage and birth information, since the informant was naturally someone other than the person who died.

Not all sources are created equal. Jones warns, “Sources can be right or wrong and the evidence gleaned from them can be of excellent or poor quality. Analysis of the evidence helps the genealogist determine whether the source is correct or not. Analysis should be very careful, because sources of apparent high quality can be wrong or vice versa.” When you thoroughly analyze the evidence and place it in the context of all the available evidence you have regarding the particular research question you’re trying to answer, you can confidently state your conclusion.

===Assessing An Ancestor’s Identity===
Three situations may arise in evaluating an ancestor’s identity:
'''
Multiple sources agree''' — All available evidence from sources such as death records and marriage records agree, such as indicating an ancestor’s parentage. Fortunately, this situation applies to most cases.

'''Evidence conflicts''' — Evidence from different sources do not agree, making the case more complicated and needing careful evaluation. Says Jones, “I found evidence of four different men as having been the father of my ancestor, Amzi Leach. Evaluating the evidence helped me conclude which of the men was the actual father.”

'''No direct source directly answers the question''' — A thorough search yields no source directly identifying an ancestor or ancestral fact. You can correlate all available evidence and draw a conclusion that meets the Genealogical Proof Standard. Jones says, “This was the case with identifying the parents of a client’s ancestor. While no record identifies the ancestor’s father directly, a combination of marriage, probate, and tax records in combination with an undocumented publication that by itself wouldn’t carry much weight, yielded an incontrovertible conclusion identifying the father.”

As you trace your ancestry, it’s likely you’ll run into the second and third situation at one time or another. I’ve run into the “Evidence conflicts” situation myself in the case of Chaim Ber Dvorkin and his relationship to my great-grandmother, Breina Dvorkin Krasner. Chaim Ber’s parents were Elias Meyer and Chaya according to his 1915 death certificate. Breina’s parents were Hillel and Michla according to her 1937 death certificate. Were Elias Meyer and Hillel Meyer the same person? I’ve evaluated naming traditions (following the eastern European practice of naming after the deceased) and tax records (no vital records exist for their ancestral home in Belarus) and came to the conclusion that Elias Meyer and Hillel Meyer are indeed the same person and father to Chaim Ber and Breina. I have not found enough evidence to draw any conclusions about the connection between mothers Chaya and Michla.

===Negative Evidence===
“As Sherlock Holmes famously pointed out, the key to a case can be the fact that a dog doesn’t bark,” wrote Mills in her June 2000 NGS Quarterly editorial. We have to know what we didn’t find but maybe should have. Donn Devine, cg, cgi of Wilmington, Delaware adds, “When you have negative evidence, you have to account for it. All too often, evidence conflicts. You need to weigh and evaluate the information. That’s a process that calls for experience.”

One example comes from Jones. He couldn’t find any Overtons in Spotsylvania Country land tax lists, even though deed records showed they owned land. His application of negative evidence resulted in: (1) the conclusion that the surname had evolved recently from Howerton; (2) the organization of seemingly unrelated individuals into family groups; and (3) the identification of earlier generations of the family.

===Importance of Citation===
I’ve always believed that citation should allow someone else to replicate your research. I’ve relied on this many times to check out some detail in my original sources. Citation also helps to organize what evidence we’ve accumulated. Says Jones, “With many sources bearing on every genealogical question, citation helps the researcher to ‘keep them straight,’ that is, to maintain a record of where each item of information and evidence comes from.”

Source citation helps evaluate the quality of the information used. For instance, a source created in the last few years about a genealogical fact from the 1820s would not seem to have much credibility.

Detailed citation can lead us to additional information. This was the case when a citation led Jones to uncatalogued manuscript material at the Cincinnati Historical Society, far from where his ancestors lived. It held a key to identifying one of his ancestors and even included letters another ancestor had written.

===Question, Question, Question===
“Don’t be afraid to question everything,” says Mills. “If no source is given, it’s obvious something’s wrong. If it doesn’t seem to hang together, find out why.” It’s all too easy to accept information as a given, without checking out the sources. It’s also helpful to learn the environmental context around your ancestors — migrations, neighbors, economic situation, etc. The amount of available secondary information has skyrocketed with the explosion of the Internet. And a lot of it has no source information. Devine says, “You have to dig deeper and replicate what someone else did. Sometimes you don’t even know where to start. If images are involved, you don’t know it they’ve been altered with a photoediting program.” Adds Jones, “If the Internet is to fulfill its potential as a valuable resource for genealogists, individuals and businesses posting information for genealogists need to provide clear and detailed source citations. Only with such citations will consumers know whether the information is useful or whether it is bunk.”

===Put It On Paper===
“It’s always good to put your reasoning on paper, especially if you’re dealing with a complicated problem,” says Devine. In addition, he often shares his thinking with fellow genealogists. “Sometimes you can convince yourself, but others say otherwise.” It’s also a good idea to photocopy information whenever possible and cite the source directly on it, so if it’s copied again, the source is there.

Devine also recommends naming the source first, before beginning to write down the information. “Otherwise it’s easy to overlook recording the citation,” he says, “and it’s also the natural way to attribute information: ‘Aunt Minnie told me…’ rather than ‘The foregoing information was provided by Aunt Minnie.’”

Jones agrees and says, “Be extremely careful to note in great detail the source for every scrap of information concerning your ancestors. While it may seem time-consuming to do this, it will save you time in the long run. The detailed source citations will enable you to evaluate and re-evaluate your evidence and come to accurate conclusions without having to search for the sources again and again.”

===Review Your Information===
I was examining my grandfather’s ship passenger record one day and noticed another passenger on the manifest from the same town. This passenger bore a surname that seemed to be linked to mine. As you gain experience, you can — and should — go back to your sources. You may make additional observations that can aid your research. And citations can make it easier to make the most of the evidence you have. Says Jones, “Typically with thorny problems, genealogists may have to go over the same ground more than once. The citations make it easier to do that.”

So take the time now to cite your sources and continue to do so as you research. Document your conclusions according to the Genealogical Proof Standard. The methodology will help you make the most of your research, while allowing other researchers to understand and replicate your work.

===The Genealogical Proof Standard: A Five-Step Process===
1. We conduct a reasonably exhaustive search for all information that is or may be pertinent to the identity, relationship, event, or situation in question;

2. We collect and include in our compilation a complete, accurate citation to the source or sources of each item of information we use;

3. We analyze and correlate the collected information to assess its quality as evidence;

4. We resolve any conflicts caused by items of evidence that contradict each other or are contrary to a proposed (hypothetically) solution to the question; and

5. We arrive at a soundly reasoned, coherently written conclusion.

Source: The BCG Standards Manual, Millennium Edition (Ancestry, 2000)

This article originally appeared in the January/February 2001 issue of Family Chronicle.
Last Updated ( Friday, 11 November 2005 )

[[Category:Genealogy|Evaluating Evidence Article]]


[[fr:Evaluer la fiabilité d'une source]]

QUAY

2008-06-07T16:32:52Z

Elliott1961:

{{glossary
| meaning = Quality of Data
| description = An assessment of the certainty of the evidence to support the conclusion drawn from evidence. Values: [0;1;2;3]
}}

[[Category:GEDCOM]]


[[fr:QUAY]]

PAGE

2008-06-07T16:28:12Z

Elliott1961:

{{glossary
| meaning = Page
| description = A number or description to identify where information can be found in a referenced work.
}}

[[Category:GEDCOM]]


[[fr:PAGE]]

NOTE RECORD

2008-05-28T05:40:28Z

Elliott1961:

The Note Record Structure is a top lever entity '''not''' used in PGV. It is a structure with possible uses where notes are aplicable to multiple records or their substructures. In PGV the [[NOTE STRUCTURE]] is always embedded in higher level entity.

NOTE_RECORD:=
n @<[[XREF:NOTE]]>@ NOTE <[[SUBMITTER_TEXT]]> {1:1}
+1 [CONC|CONT] <[[SUBMITTER_TEXT]]> {0:M}
+1 REFN <[[USER_REFERENCE_NUMBER]]> {0:M}
+2 TYPE <[[USER_REFERENCE_TYPE]]> {0:1}
+1 RIN <[[AUTOMATED_RECORD_ID]]> {0:1}
+1 <<[[SOURCE_CITATION]]>> {0:M}
+1 <<[[CHANGE_DATE]]>> {0:1}

[[Category:GEDCOM]]
[[Category: Gedcom Structures]]


[[fr: ENREGISTREMENT_NOTE]]

CHANGE DATE

2008-05-26T05:43:35Z

Elliott1961:

The Change Date Structure is intended to record the last change to the record.

CHANGE_DATE:=
n CHAN {1:1}
+1 DATE <[[CHANGE_DATE]]> {1:1}
+2 TIME <[[TIME_VALUE]]> {0:1}
+1 <<[[NOTE_STRUCTURE]]>> {0:M}

[[Category:GEDCOM]]
[[Category: Gedcom Structures]]


[[fr: DATE MODIFICATION]]

ADDRESS STRUCTURE

2008-05-25T12:02:19Z

Elliott1961:

The address should be formed as it would appear on a mailing label using the ADDR and the CONT lines, which are required, as the address is not expected to have only one line. The additional, optional tags (ADDR1...CTRY) can be used in systems that have structured Address indexing.

The Address Structure as defined in the GEDCOM 5.5.1 standard, should be used in as substructure of Residence (RESI) event, and well as of other events, not as a ''standalone'' Event:

ADDRESS_STRUCTURE:=
n ADDR <[[ADDRESS_LINE]]> {1:1}
+1 CONT <[[ADDRESS_LINE]]> {0:3}
+1 ADR1 <[[ADDRESS_LINE1]]> {0:1}
+1 ADR2 <[[ADDRESS_LINE2]]> {0:1}
+1 ADR3 <[[ADDRESS_LINE3]]> {0:1}
+1 CITY <[[ADDRESS_CITY]]> {0:1}
+1 STAE <[[ADDRESS_STATE]]> {0:1}
+1 POST <[[ADDRESS_POSTAL_CODE]]> {0:1}
+1 CTRY <[[ADDRESS_COUNTRY]]> {0:1}
n PHON <[[PHONE_NUMBER]]> {0:3}
n EMAIL <[[ADDRESS_EMAIL]]> {0:3}
n FAX <[[ADDRESS_FAX]]> {0:3}
n WWW <[[ADDRESS_WEB_PAGE]]> {0:3}

[[Category:GEDCOM]]
[[Category: Gedcom Structures]]


[[fr: STRUCTURE DE L'ADRESSE]]

XREF:REPO

2008-05-25T11:54:28Z

Elliott1961:

An [[XREF:REPO]] is a pointer to, or an unique identifier of, a [[REPOSITORY RECORD|repository record]], for example ''R123''. In Gedcom it always appears enclosed in @ symbols, e.g. ''@R123@''

[[XREF:REPO]]

[[Category:GEDCOM]]


[[fr: XREF:REPO]]

REPOSITORY RECORD

2008-05-25T07:15:07Z

Elliott1961:

The [[REPOSITORY RECORD]] collects the information relating to a location where a source may be found. This repository could be almost anything, including a library, home, website, or government agency.

REPOSITORY_RECORD: =
n @<[[XREF:REPO]]>@ REPO {1:1}
+1 NAME <[[NAME_OF_REPOSITORY|NAME_OF_REPOSITORY]]> {0:1}
+1 <<[[ADDRESS_STRUCTURE|ADDRESS_STRUCTURE]]>> {0:1}
+1 <<[[NOTE_STRUCTURE|NOTE_STRUCTURE]]>> {0:M}
+1 REFN <[[USER_REFERENCE_NUMBER|USER_REFERENCE_NUMBER]]> {0:M}
+2 TYPE <[[USER_REFERENCE_TYPE|USER_REFERENCE_TYPE]]> {0:1}
+1 RIN <[[AUTOMATED_RECORD_ID|AUTOMATED_RECORD_ID]]> {0:1}
+1 <<[[CHANGE_DATE|CHANGE_DATE]]>> {0:1}

[[Category:GEDCOM]]
[[Category: Gedcom Structures]]


[[fr: ENREGISTREMENT DU DEPOT D'ARCHIVES]]

SOURCE REPOSITORY CITATION

2008-05-24T21:01:51Z

Elliott1961:

The Source Repository Citation structure is used within a source record to point to the [[REPOSITORY RECORD]], specifying in addition a possible call number or other formal ID of the source within repository.

SOURCE_REPOSITORY_CITATION:=
n REPO [ @XREF:REPO@ | <NULL>] {1:1}
+1 <<[[NOTE_STRUCTURE]]>> {0:M}
+1 CALN <[[SOURCE_CALL_NUMBER]]> {0:M}
+2 MEDI <[[SOURCE_MEDIA_TYPE]]> {0:1}

[[Category:GEDCOM]]
[[Category: Gedcom Structures]]


[[fr: CITATION DU DEPOT D'ARCHIVES DE LA SOURCE]]

NOTE STRUCTURE

2008-05-19T05:42:40Z

Elliott1961:

A NOTE_STRUCTURE is a free form field for adding any comments or notes on a piece of data in the GEDCOM file. There are two possible formats for this structure:
* embedded - the entire note structure is embedded within the piece of data it supports and 'n' is one higher than the level of the supported data.
* linked - the subrecord is merely a link to a [[NOTE_RECORD]], which is like an embedded NOTE_STRUCTURE but stands alone at level zero.
PhpGedView uses the embedded style exclusively. On import of a linked style, PhpGedView will .....

NOTE_STRUCTURE:=
[
n NOTE @<[[XREF:NOTE]]>@ {1:1} (linked)
|
n NOTE [<[[SUBMITTER_TEXT|SUBMITTER_TEXT]]> | <NULL>] {1:1} (embedded)
+1 [CONC|CONT] <[[SUBMITTER_TEXT|SUBMITTER_TEXT]]> {0:M}
]

[[Category:GEDCOM]]
[[Category: Gedcom Structures]]


[[fr: NOTE_STRUCTURE]]

AGNC

2008-05-18T07:49:16Z

Elliott1961:

{{glossary
| meaning = Agency
| description = The institution or individual having authority and/or responsibility to manage or govern.
}}

[[Category:GEDCOM]]
[[Category:GEDCOM tags]]


[[fr: AGNC]]

PLAC

2008-05-17T13:46:05Z

Elliott1961:

{{glossary
| meaning = Place
| description = A jurisdictional name to identify the place or location of an event.
}}

[[Category:GEDCOM]]


[[fr: PLAC]]

SOURCE RECORD

2008-05-17T13:45:57Z

Elliott1961:

The [[SOURCE RECORD]] collects information about something that provides evidence for information in the [[GEDCOM]] file. This item could be a newspaper, magazine, microfilm, letter or even a phone conversation. It's important to add as much information as possible to this record to allow other researches to locate your sources and verify your information.

SOURCE_RECORD: =
n @<[[XREF:SOUR]]>@ [[SOUR]] {1:1}
+1 [[DATA]] {0:1}
+2 [[EVEN]] <[[EVENTS_RECORDED|EVENTS_RECORDED]]> {0:M}
+3 [[DATE]] <[[DATE_PERIOD|DATE_PERIOD]]> {0:1}
+3 [[PLAC]] <[[SOURCE_JURISDICTION_PLACE|SOURCE_JURISDICTION_PLACE]]> {0:1}
+2 [[AGNC]] <[[RESPONSIBLE_AGENCY|RESPONSIBLE_AGENCY]]> {0:1}
+2 <<[[NOTE_STRUCTURE]]>> {0:M}
+1 [[AUTH]] <[[SOURCE_ORIGINATOR|SOURCE_ORIGINATOR]]> {0:1}
+2 <nowiki>[</nowiki>[[CONT]]|[[CONC]]<nowiki>]</nowiki> <[[SOURCE_ORIGINATOR|SOURCE_ORIGINATOR]]> {0:M}
+1 [[TITL]] <[[SOURCE_DESCRIPTIVE_TITLE|SOURCE_DESCRIPTIVE_TITLE]]> {0:1}
+2 <nowiki>[</nowiki>[[CONT]]|[[CONC]]<nowiki>]</nowiki> <[[SOURCE_DESCRIPTIVE_TITLE|SOURCE_DESCRIPTIVE_TITLE]]> {0:M}
+1 [[ABBR]] <[[SOURCE_FILED_BY_ENTRY|SOURCE_FILED_BY_ENTRY]]> {0:1}
+1 [[PUBL]] <[[SOURCE_PUBLICATION_FACTS|SOURCE_PUBLICATION_FACTS]]> {0:1}
+2 <nowiki>[</nowiki>[[CONT]]|[[CONC]]<nowiki>]</nowiki> <[[SOURCE_PUBLICATION_FACTS|SOURCE_PUBLICATION_FACTS]]> {0:M}
+1 [[TEXT]] <[[TEXT_FROM_SOURCE|TEXT_FROM_SOURCE]]> {0:1}
+2 <nowiki>[</nowiki>[[CONT]]|[[CONC]]<nowiki>]</nowiki> <[[TEXT_FROM_SOURCE|TEXT_FROM_SOURCE]]> {0:M}
+1 <<[[SOURCE_REPOSITORY_CITATION|SOURCE_REPOSITORY_CITATION]]>> {0:1}
+1 <<[[MULTIMEDIA_LINK|MULTIMEDIA_LINK]]>> {0:M}
+1 <<[[NOTE_STRUCTURE|NOTE_STRUCTURE]]>> {0:M}
+1 [[REFN]] <[[USER_REFERENCE_NUMBER|USER_REFERENCE_NUMBER]]> {0:M}
+2 [[TYPE]] <[[USER_REFERENCE_TYPE|USER_REFERENCE_TYPE]]> {0:1}
+1 [[RIN]] <[[AUTOMATED_RECORD_ID|AUTOMATED_RECORD_ID]]> {0:1}
+1 <<[[CHANGE_DATE|CHANGE_DATE]]>> {0:1}

[[Category:GEDCOM]]
[[Category: Gedcom Structures]]


[[fr: Enregistrement d'une source]]

DATE

2008-05-17T10:21:13Z

Elliott1961:

{{glossary
| meaning = Date
| description = The time of an event in a calendar format.
}}

[[Category:GEDCOM]]
[[Category:GEDCOM tags]]


[[fr: DATE]]

XREF:SOUR

2008-05-17T06:48:29Z

Elliott1961:

An [[XREF:SOUR]] is a pointer to, or an unique identifier of, a [[SOURCE RECORD|source record]], for example ''S123''. In Gedcom it always appears enclosed in @ symbols, e.g. ''@S123@''

[[XREF:SOUR]]

[[Category:GEDCOM]]



[[fr:XREF:SOUR]]

OBJE

2008-05-15T05:28:17Z

Elliott1961:

{{glossary
| meaning = Object
| description = Pertaining to a grouping of attributes used in describing something. Usually referring to the data required to represent a multimedia object, such an audio recording, a photograph of a person, or an image of a document.
}}

[[Category:GEDCOM]]

[[fr:OBJE]]

TEXT

2008-05-14T05:46:36Z

Elliott1961:

{{glossary
| meaning = Text
| description = The exact wording found in an original source document.
}}

[[Category:GEDCOM]]


[[fr:TEXT]]

CALN

2008-05-14T05:37:37Z

Elliott1961:

{{glossary
| meaning = Call Number
| description = The number used by a repository to identify the specific items in its collections.
}}

[[Category:GEDCOM]]
[[Category:GEDCOM tags]]


[[fr:CALN]]

REPO

2008-05-13T05:41:29Z

Elliott1961:

{{glossary
| meaning = Repository
| description = An institution or person that has the specified item as part of their collection(s).
}}

[[Category:GEDCOM]]

[[fr:TITL]]

PUBL

2008-05-12T18:54:03Z

Elliott1961:

{{glossary
| meaning = Publication
| description = Refers to when and/or were a work was published or created.
}}

[[Category:GEDCOM]]

[[fr:PUBL]]

AUTH

2008-05-12T14:50:57Z

Elliott1961:

{{glossary
| meaning = Author
| description = The name of the individual who created or compiled information.
}}

[[Category:GEDCOM]]
[[Category:GEDCOM tags]]


[[fr:AUTH]]

ABBR

2008-05-12T14:41:46Z

Elliott1961:

{{glossary
| meaning = Abbreviation
| description = A short name of a title, description, or name.
}}

[[Category:GEDCOM]]
[[Category:GEDCOM tags]]


[[fr:ABBR]]

SOUR

2008-05-12T09:41:46Z

Elliott1961:

{{glossary
| meaning = Source
| description = The initial or original material from which information was obtained.
}}

== See Also ==

* [[Adding a Source]]

[[Category:GEDCOM]]


[[fr:SOUR]]

Facts and Events

2008-04-12T07:21:11Z

Elliott1961:

The naming conventions in Gedcom standard have „Events” and „Facts” (sometimes called „Attributes”). They can both apply to individuals and families. The conceptual difference between events and facts is that '''Events''' occur at a definite point in time (while the point may extend as far as a day), while '''Facts''' are either extended in time, or don't have a specific time attached to them. The real life and the reality of information gathering blurs somewhat this distinction. An example of a definite '''Event''' is birth, which occurs at a specific time and place (even if date or place is unknown, we expect this to be self-evident). A definite '''Fact''' could be Number of Children for an individual or family: we usually do not assign a date to such number. However, if you describe the education, you can use the „Education” '''Fact''' extended in time, or „Graduation” '''Event''', or both. A person's medal or distinction can be described as fact of having or as event of receiving this medal or distinction, etc.

Facts and Events are designated in Gedcom by Tags - short, 4 character labels that are visible in the Gedcom file, and by descriptive names. There is a number of pre-defined Events tags, like Birth (BIRT) for individual or Marriage (MARR) for family, and a generic „Event” (EVEN) tag. There is also a number of pre-defined Facts (Attributes) like Residence (RESI) or Number Of Children (NCHI), and a generic „Fact” (FACT) tag. There can be also non-standard tags, some of which are used in PGV, for example Military (_MILI); they are preceded by an underline character to distinguish them from standard tags. If possible, try to use the available, pre-defined tags (standard or non-standard), as there is a better chance that they will be understood by PGV and processed by other software that may use the Gedcom file, and resort to generic FACT or EVEN only if existing tags won't do.

Events and facts can aply to an individual, family or both. Family events and facts are displayed by PGV for both spouses (but not for children). The Administrator can configure the system to select the facts and events you can add, and whether multiples can be added.

When entering a fact and event you are presented with a list of fields (tags), to fill. The [[Common Data Elements|commonly encountered elements]] are described separately, and will not be repeated here except to indicate the differences.

==Life and death==
;Birth ([[BIRT]])
: You should include as much details as possible for the birth event: date and time, place, address, and all associates. Birth was often recorded together with christening, see the Christening event.
;Death ([[DEAT]])
: Record here all details of death, date, place, etc. You can also record the cause of death and age at death, useful if exact date is not known.
;Burial ([[BURI]])
: Record the burial details. Cementery can be added as (non-standard) tag; you can also put cemetary as the most detailed element of Place data.
;Cremation ([[CREM]])
: Cremation has its own tag, with similar details as Burial (except for cementery)

==Family related==
;Number of Children ([[NCHI]])
:Sometimes the number of children is known, but not their names (or not all of them). Put here the total number irrespective of listing some of them. When zero is used, it indicates childless family or person. When applied to an individual, designates the total number of children of this person. When applied to a family, it is the total number of children in this family.
;Number of Marriages ([[NMR]])
: Indicates the number of marriages for this individual. Not necessary if all the marriages are known and described in the database. Use zero to indicate that the person never married.
;Adoption ([[ADOP]])
: The adoption event applies to individual (adoptee), and allows you to specify if the husband, wife or both adopted the child. In addition to the adoption event, you should record the role of the child (Pedigree:adopted) when adding him/her to a family.

===Marriage===

;Marriage ([[MARR]])
:For married couple, the marriage event should be added, even if no details are known (only the „yes” checkbox is checked then). You can add marriage details (time, place, address stc) and indicate the type of marriage if known – a list is provided:
:*Civil marriage
:*Religious marriage
:*Registered partnership
:Selecting Religious marriage, Civil Marriage or Registered Partnership from the list is equivalent to selecting the type of marriage as above.
;Divorce ([[DIV]])
:Note here the event of dissolving a marriage - typically through civil action.

'''Other events''' related to marriage; some of them, like Announcement and Bann or Settlement and Contract appear to duplicate each other, usually it is sufficient to select one of them:

:;Engagement ([[ENGA]])
::Recording or announcing an agreement between two people to become married.
:;Marriage Bann ([[MARB]])
::An official public notice given that two people intend to marry.
:;Marriage License ([[MARL]])
::An event of obtaining a legal license to marry.

:;Marriage Settlement ([[MARS]])
::An agreement between two people contemplating marriage, at which time they agree to release or modify property rights that would otherwise arise from the marriage.

:;Marriage Contract ([[MARC]])
::Recording a formal agreement of marriage, including the prenuptial agreement in which marriage partners reach agreement about the property rights of one or both, securing property to their children.

:;Divorce Filled ([[DIVF]])
::Filing for a divorce by a spouse.

:;Annulment ([[ANUL]])
::Declaring a marriage void from the beginning.
==Lifetime achievements and facts==
;Residence ([[RESI]])
:A preferred way of entering the address data for individual or family. You can indicate, when person or family lived at this location or, for current residence, only the starting point (from...). Enter Place using the [[Place data|rules for place names]], and the following fields if known:

:;Address ([[ADDR]])
:;Fax number ([[FAX]])
:;Phone number ([[PHON]])
:;Email address ([[EMAI]])
:;Web page ([[WWW]])

:PGV allows you also to add the above tags in non-standard way, as personal attributes (not as sub-tags of the Residence fact), and will display them if found in Gedcom file. While not strictly following standards, it is sometimes useful to attach data like email and cell phone number to a person, not location (Residence), since they tend to move around with a person rather than stay with an address.

;Education ([[EDUC]])
: The education data (fact) for individual. The ''Education'' tag is used to describe the education level (high School, university etc.). Enter the name of the school in the ''Agency'' field, add dates (From...To) and ''Address'' if known.
;Graduation ([[GRAD]])
: The graduation event accepts the ''Type'' tag describing the level, ''Agency'' for school name and ''Address''. As for all events, enter the date of graduation.
;Occupation ([[OCCU]])
: The Occuation fact describes the occupation and/or job for individual. The ''Occupation'' tag is used to escribe the occupation name or jub title, ''Agency'' tag contains the name of the employer, with address, phone etc. tags available as well. Use date interval to indicate the term of employment or occupation.
;Retirement ([[RETI]])
:Describes the Retirement event, using date, ''Agency'' for employer name, and place data.

;Military ([[_MILI]])
: A general fact or event used to describe any military involvement, campaing, service etc. Use the ''Military'' and ''Type'' tags to describe the event or fact, ''Agency'' to descibe the military unit pertaining to the fact. This is a non-standard tag.

;Physical Description ([[DSCR]])
:The physical description of a person (e.g. ''Tall, dark and handsome'' or ''Brown Hair, Blue Eyes, Height 165 cm'') in lieu of photograph of a portrait. A date can be attached to this fact to indicate the time the description was in effect.

==National / government==
;Nationality ([[NATI]])
:Enter the national or tribal origin of the individual here.

;Imigration ([[IMMI]])
:Defined in the Gedcom as „an event of entering into a new locality with the intent of residing there”, may also be used independently of the intent, if the fact of residence in another place was established. Supply the date of the event and the (first) new place of residence. See also Emigration.

;Emigration ([[EMIG]])
:Defined in the Gedcom as „an event of of leaving one's homeland with the intent of residing elsewhere.”. Linked with Emigration, can be described as either. For Emigration, supply the date of leaving the country of origin, and possibley the place (e.g .port) of departure.

;Naturalization ([[NATU]])
:Record here the date and place of the event of obtaining a (new) citizenship.

;Census ([[CENS]])
:Census is the periodic count of the population for a nation or state. Note here when and were the census count, applicable to the person or family, took place; you can also add an Address and age of the individual if mentioned in census document. Census documents are valuable search tools, and they are usually also desribed as [[Proper use of sources|Sources]] of personal data.

;Social Security Number ([[SSN]])
:United States Social Security number, commonly used an national ID number for individuals. By default it is hidden from all but the Administrators, and is not shown in the PGV display. As all others, this setting is configurable.

;National ID Number ([[IDNO]])
:A nationally-controlled number assigned to an individual; requires a Type to define national system and type of the ID. The US Social Security has its own tag (see SSN above). If used, privacy settings can be applied to hide it from view.

==Earthly posessions and titles==
;Property ([[PROP]])
:This is the place to list real estate and other significant possessions of an individual. Construed as „Fact”, but can also be used as an „Event” of acquiring such possesion. The ''Property'' field is used to list the property (properties) being described.

;Title ([[TITL]])
:Used to enter the title given to (or used by) a person, typically of noble class, royalty etc. ''Prince'', ''Duke'', ''Marquis'', ''Baron'', ''Rajah'', ''Emir'' are just few examples of this vast domain of [http://en.wikipedia.org/wiki/Royal_and_noble_ranks nobility ranks.]

;Will ([[WILL]])
:Notes an existence of the will - a legal document, by which a person disposes of his or her estate, to take effect after death. It is treated as an „Event”: enter date and place of signing the document. See also Probate.

;Probate ([[PROB]])
:If the court determined that the ''Will'' is valid, note the fact here. Put a date of final determination, and note any intermediate court proceedings in Notes)

==Religious and social==

As the Gedcom standard was originally created by ''The Church of Jesus Christ of Latter-day Saints'' (LDS), it is perhaps not surprising that many of the events describe the christian rites and ordinances. With some creativity, however, one can use them to record events and rites in other religies as well.

;Religious afiliation ([[RELI]])
: Name of religion with which the person is affiliated. Can be used as a „Fact” or as „Event” - in the second case supply the date when the affiliation occured (in infancy or later in life).

;Christening ([[CHR]])
:Christening is a ceremony of baptizing and naming a child. Naming of a child appears to be universal in most cultures, and one can use this tag (possibly with an added ''Type'') to indicate Jewish ''Zeved Habat'' or ''Brit Milah'', Hindu ''Namskaran Samskar'', Chinese ''Red Egg'' or Egyptian ''Sebou''. See Wikipedia entries for [http://en.wikipedia.org/wiki/Infant_baptism Infant baptism],and for [http://en.wikipedia.org/wiki/Naming_ceremony Naming ceremony]. Enter date and place of the event.

;Baptism ([[BAPM]])
:Baptism is a is the sacramental act of cleansing in water (that typically also admits one as a full member of the church). While a principal rite of Christianity, it has roots and equivalents in [http://en.wikipedia.org/wiki/Baptism#Other_initiation_ceremonies other cultures], and can be used as such.

;Adult Christening ([[CHRA]])
:The religious event of baptizing an adult person – see [http://en.wikipedia.org/wiki/Baptism baptism] entry in Wikipedia.

;Bar Mitzvah ([[BARM]])
:Coming of age event and [http://en.wikipedia.org/wiki/Bar_mitzvah ceremony] held when a Jewish boy reaches age 13.

;Bas Mitzvah ([[BASM]])
:Coming of age event and [http://en.wikipedia.org/wiki/Bar_mitzvah| ceremony] held when a Jewish girl reaches age 13.

;Blessing ([[BLES]])
:A religious event of bestowing divine care or intercession. [http://en.wikipedia.org/wiki/Blessing Blessing] is a universal term and is applicable to many cultures and faiths.

;First Communion ([[FCOM]])
:A [http://en.wikipedia.org/wiki/First_Communion Christian rite], the first act of sharing in the Lord's supper as part of church worship.

;Ordination ([[ORDN]])
:The [http://en.wikipedia.org/wiki/Ordination process] by which individuals are consecrated, that is set apart as clergy to perform various religious rites and ceremonies in Christianity, Judaism, Islam, Buddhism etc.

;Ordinance ([[ORDI]])
:Enter other religious facts and events under this heading.

;Confirmation ([[CONF]])
:The [http://en.wikipedia.org/wiki/Confirmation religious event] in many Christian churches of conferring the gift of the Holy Ghost and, among protestants, full church membership.

;Caste ([[CAST]])
:A name assigned to a [http://en.wikipedia.org/wiki/Caste particular group] (racial group, religious group, a group with an inherited status etc.) that this person was associated with.

===LDS specfic events===
Read more in the Wikipedia articles about the [http://en.wikipedia.org/wiki/Portal:Latter-day_Saints LDS church] and the [http://en.wikipedia.org/wiki/Sealing_(Latter_Day_Saints) sealing ceremonies].

;LDS Child Sealing ([[SLGC]])
:Sealing of a child to his or her parents in an LDS temple ceremony.
;LDS Spouse Sealing ([[SLGS]])
:Sealing of a husband and wife in an LDS temple ceremony.

;LDS Babtism ([[BAPL)
:Baptism performed at age eight or later by priesthood authority of the LDS Church.
;LDS Confirmation ([[CONL]])
:The religious event by which a person receives membership in the LDS Church.

;LDS Endowment ([[ENDL]])
:An endowment ordinance for an individual performed in an LDS temple.

==Generic==

There are two generic tags, unsurprisingly called Fact and Event.
; Fact ([[FACT]])
: Any fact that does not have its own definition. Requires a Type ([[TYPE]]) subordinate tag to specify the type of fact, while the Event tag contains the fact name.
; Event ([[EVEN]])
: Any event that does not have its own definition. Requires a Type ([[TYPE]]) subordinate tag to specify the type of fact. You can add date and place to the generic Event.

In addition to generic fact and event, many genealogy programs define the custom tags. The tags that are not recognized by PGV will still be displayed, but marked as an error. The Administrator can change this behaviour, and also configure non standard tags to be recognized by PGV, see [[Inside info#Non-standard GEDCOM codes|Non-standard GEDCOM codes]].

[[fr:Faits et détails personnels]]