Search results

Jump to navigation Jump to search
  • [[Category:GEDCOM]] [[Category: Gedcom Structures]]
    61 bytes (6 words) - 04:11, 28 March 2008
  • ...e Header and one Trailer the Gedcom file contains nothing but records. The structures within records describe the record content and can reference other records. [[Gedcom data structure]]
    958 bytes (121 words) - 09:18, 19 October 2008
  • This part describes the overall structure of the Gedcom file: one header (required), optional submission record, one to many record [[Category:GEDCOM]]
    361 bytes (41 words) - 10:38, 3 April 2008
  • ...n individual or organization that contributed information contained in the GEDCOM file. [[Category:GEDCOM]]
    593 bytes (54 words) - 15:21, 19 October 2008
  • [[Category:GEDCOM]] [[Category: Gedcom Structures]]
    349 bytes (58 words) - 09:12, 29 October 2008
  • [[Category:GEDCOM]] [[Category: Gedcom Structures]]
    335 bytes (42 words) - 07:43, 26 May 2008
  • [[Category:GEDCOM]] [[Category: Gedcom Structures]]
    793 bytes (74 words) - 22:50, 28 March 2008
  • [[Category:GEDCOM]] [[Category: Gedcom Structures]]
    725 bytes (80 words) - 22:42, 28 March 2008
  • This is the structure of the Place element in Gedcom 5.5.1. In addition to PLAC tag, it contains optional FORM, Fonetic variatio [[Category:GEDCOM]]
    787 bytes (78 words) - 04:46, 28 March 2008
  • [[Category:GEDCOM]] [[Category: Gedcom Structures]]
    549 bytes (73 words) - 23:01, 24 May 2008
  • [[Category:GEDCOM]] [[Category: Gedcom Structures]]
    545 bytes (84 words) - 19:10, 27 October 2008
  • ...ication between Ancestral File download requests and [[TempleReady]]. Each GEDCOM transmission file should have only one submission record. The format of the optional submission record of a GEDCOM file follows.
    1 KB (135 words) - 21:35, 30 March 2008
  • [[Category:GEDCOM]] [[Category: Gedcom Structures]]
    664 bytes (86 words) - 13:36, 25 October 2008
  • ...p information. The notation has been invented many times, examples of such structures abound: the directory and file system in your computer is a typical example ...ed by an incremented number. The XML example above could look like this in Gedcom,
    5 KB (671 words) - 22:58, 9 May 2009
  • [[Category:GEDCOM]] [[Category: Gedcom Structures]]
    697 bytes (88 words) - 07:40, 28 May 2008
  • [[Category:GEDCOM]] [[Category: Gedcom Structures]]
    819 bytes (95 words) - 09:15, 25 May 2008
  • ...inked 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 in Gedcom==
    4 KB (621 words) - 22:54, 4 October 2008
  • [[Category:GEDCOM]] [[Category: Gedcom Structures]]
    1 KB (107 words) - 04:12, 28 March 2008
  • ...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: [[Category:GEDCOM]]
    911 bytes (134 words) - 07:42, 19 May 2008
  • The Address Structure as defined in the GEDCOM 5.5.1 standard, should be used in as substructure of Residence (RESI) event [[Category:GEDCOM]]
    1 KB (144 words) - 14:02, 25 May 2008
  • Note that GEDCOM technically only allows one nickname.  If you do have more than one, h [[Category:GEDCOM]]
    2 KB (193 words) - 04:11, 24 November 2008
  • ...nformation about something that provides evidence for information in the [[GEDCOM]] file. This item could be a newspaper, magazine, microfilm, letter or eve [[Category:GEDCOM]]
    2 KB (230 words) - 15:45, 17 May 2008
  • [[Category:GEDCOM]] [[Category: Gedcom Structures]]
    2 KB (180 words) - 22:08, 1 November 2008
  • [[Category:GEDCOM]] [[Category: Gedcom Structures]]
    1 KB (175 words) - 18:09, 26 October 2008
  • [[Category:GEDCOM]] [[Category: Gedcom Structures]]
    2 KB (201 words) - 18:27, 26 October 2008
  • ...| description = This feature is meant to hide certain facts, identified by GEDCOM tags, for all individuals alive or dead. By default the SSN tag is hidden t ::A list displays the Gedcom tags and corresponding Fact and Event names to select the one that should b
    2 KB (379 words) - 05:19, 7 April 2008
  • [[Category:GEDCOM]] [[Category: Gedcom Structures]]
    3 KB (391 words) - 04:12, 28 March 2008
  • ;[[GEDCOM SOAP Web Service API]] :Information on access PhpGedView data through a SOA ;[[GEDCOM REST Web Service API]] :Information on access PhpGedView data through a RES
    4 KB (681 words) - 01:23, 1 December 2010
  • | colspan = 2 | GEDCOM 5.5 The data model is built up around the GEDCOM 5.5 specification. The controller consists of an API written in PHP that al
    9 KB (1,509 words) - 19:03, 7 June 2010
  • You may need to clear the cache. This can be done from the "Customize this GEDCOM Welcome page" link on the welcome page. Click the Clear Cache button at the ...d also delete your cache files. This can be done from the "Customize this GEDCOM Welcome page" link (on the welcome page) or by manually deleting the files
    9 KB (1,496 words) - 17:33, 16 May 2010
  • This article describes common data elements: fields and structures, that are encountered in creating most [[Facts and Events]] concerning an i ...elds 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;
    4 KB (709 words) - 08:10, 18 July 2008
  • ...n the Gedcom data using the [[Setting a Restriction|Restriction]] tag. The Gedcom Privacy configuration screen is divided into sections. ...w web site. Check under the page title whether you are editing the correct GEDCOM.
    12 KB (1,998 words) - 17:29, 30 May 2010
  • ...pages. They are generated from specific LAT/LONG tags added to places in a GEDCOM file.'' ...erences to "All"<br>instead of "Personal facts and details" This is in the GEDCOM configuration under<br>Display & Layout - Default tab to show on individual
    25 KB (4,214 words) - 19:38, 21 December 2009