RetroGen – Rethinking and Rework

I have been rethinking my approach to common gedcom tags such as notes and media, and the fact that media can have notes, to rework some of my logic. There is an old premise that the simple solutions are the best and when the logic of ones code is looking overtly complicated, it is sadly time to rethink, replan and redo ones work. My recoding approach has worked well for header and submitter tags, and tomorrow, I will brace myself for the more complex nature of redoing individuals tags (and latter still, families, repository, sources, events, media etc).

I have updated the entity relationship diagram as it contains a consolidated event files.

******************************************************************
*     ┌────────────┐      ┌────────────┐      ┌────────────┐     *
*     │ Individual │      │   Event    │      │  Citation  │     *
*     ├────────────┤      ├────────────┤      ├────────────┤     *
*     │Id      (PK)├──┬──>┤Id+No.  (PK)├─────>┤Id+No.  (PK)│     *
*     │Name        │  ├──>┤Id+Tag  (SK)├─────>┤IdTagEv#(SK)│     *
*     │Sex         │  │   │Date        │      │Source Id   ├────┐*
*     │Birth Date  │  │   │Place       │      │Details     │    │*
*     │Death Date  │  │   │Details     │      │Apid        │    │*
* ┌───┤Child Family│  │   │Type        │      │Ref Note Id ├──┐ │*
* │┌──┤SpouseFamily│  │   │Ref Note Id ├───┐  │InlineRefId ├──┤ │*
* ││  │Ref Note Id ├──(─┐ │InlineNoteId├───┤  │Media Id    ├──(┐│*
* ││  │InlineNoteId├──(─┤ │Media Id    ├─┐ │  └────────────┘  │││*
* ││  │Media Id    ├─┐│ │ └────────────┘ │ │  ┌────────────┐  │││*
* ││  └────────────┘ ││ └────────────────(─┤  │    Note    │  │││*
* ││  ┌────────────┐ ││   ┌────────────┐ │ │  ├────────────┤  │││*
* ││  │   Family   │ ││   │ Repository │ │ ├─>┤Id+No.  (PK)├<─┤││*
* ││  ├────────────┤ ││   ├────────────┤ │ │  │Data        │  │││*
* ││  │Id (PK)     ├─(┘┌─>┤Id      (PK)│ │ │  │Newline CONT│  │││*
* │├─>┤Husband Id  │ │ │  │Name        │ │ │  └────────────┘  │││*
* │└─>┤Wife Id     │ │ │  │Address     │ │ │  ┌────────────┐  │││*
* └──>┤Child Id    │ │ │  │Ref Note Id ├─(─┤  │   Media    │  │││*
*     │Ref Note Id ├─(─(─┐│InlineNoteId├─(─┤  ├────────────┤  │││*
*     │InlineNoteId├─(─(─┤└────────────┘ ├─(─>┤Id      (PK)├<─(┤│*
*     │Media Id    ├─┴─(─(───────────────┤ │  │File        │  │││*
*     └────────────┘   │ └───────────────(─┤  │Form        │  │││*
*     ┌────────────┐   │                 │ │  │Title       │  │││*
*     │   Source   │   │                 │ │  │Ref Note Id ├──┤││*
*     ├────────────┤   │                 │ │  │InlineNoteId├──┘││*
*     │Id      (PK)├<──(─────────────────(─(─┐└────────────┘   ││*
*     │_Author     │   │                 │ │ │┌────────────┐   ││*
*     │Publisher   │   │                 │ │ ││ Submitter  │   ││*
*     │Repo Id     ├───┘                 │ │ │├────────────┤   ││*
*     │ReferenceNo.│                     │ │ ││Id      (PK)│   ││*
*     │APID        │                     │ │ ││Name        │   ││*
*     │Repo Name   │                     │ │ ││Address     │   ││*
*     │Call Number │                     │ │ ││Media Id    ├───┘│*
*     │Ref Note Id ├─────────────────────(─┤ │└────────────┘    │*
*     │InlineNoteId├─────────────────────(─┘ └──────────────────┘*
*     │Media Id    ├─────────────────────┘                       *
*     └────────────┘             Note: Gedcom and Header omitted.*
******************************************************************

Update; I have changed the processing to include using a stack of gedcom tags. When a higher-level gedcom tag is encountered, the parent (or prior) tag is pushed onto the stack. The child tags can be processed whilst referencing the parent on the stack and when a lower-level tag is encountered later on, the top value on the stack is popped, so the prior parent is apparent for use.

1 SOUR FTM
2 VERS 24.0.0.1230
2 NAME Family Tree Maker for Windows
2 CORP The Software MacKiev Company
3 ADDR 30 Union Wharf,
4 CONT Boston, MA 02109,
4 CONT USA.
3 CITY Boston
3 STAE MA
3 POST 02109
3 CTRY USA
2 PHON (617) 227-6681
2 EMAIL support@familytreemaker.com
2 FAX (617) 227-6680
2 WWW www.familytreemaker.com
1 DEST FTM
1 DATE 28 Sep 2019
1 CHAR UTF-8
1 FILE FTM2019.ged
1 SUBM @SUBM@
1 GEDC
2 VERS 5.5.1
2 FORM LINEAGE-LINKED

For example, when the gedcom line of ‘3 ADDR 30 Union Wharf,’ is processed, there was a change (or increase) in gedcom level, so the ‘CORP’ tag is pushed onto the stack. When the ‘CONT’ tags are processed, again there was a change (oe increase) in gedcom levels, so the parent ‘ADDR’ tag was also pushed to the stack. When the ‘CITY’ tag is processed, this resulted in a lower-leveled tag, so the top value of ‘ADDR’ is pushed from the stack, so the prior parent of ‘CORP’ is top of stack for the processing of ‘CITY’ through ‘CTRY’.

The use of the stack makes the logic of differing levels are processing of tags appropriate to each level more viable and straight-forward.