Search Forums
Kiwitrees on Twitter

    upgrade, save settings, ID facts, spouse, installation, googlemaps, random_media, time, css, blocks, merge, add missing death, Administration, partner, shared note, kiwitrees 2.0.2, session, Search and replace, php 7, fact, 500, family fact, not married, login failure, 5.6, logout, abbreviate, fixing errors, kiwitrees, CHR, errors, internal messaging, census, descendant, prison, family, PHP, individual resource, cousins, progress, census assistant, Extra menus, slideshow, data errors, family facts, updates, name, google, 3.3.1, .mo, duplicates, Default record, style, Advanced search, new feature, 3.2.3, redirect, server, check, mobile


    122 posts


    This question sent me back to look at the GEDCOM standard. It parallels my personal thought.

    I consider BAPM and CHR the same event and on the occasion of a merge, convert CHR events to BAPM as my personal choice as the default event.

    I treat BURI and CREM as two distinct events generally for the reason you stated. I think some religions and other traditions only allow cremation when burial or placement in a Columbarium follow. I currently report placement in a Columbarium as a burial.

    Dealing with these two events, really hasn’t been a big issue for me. It is just another challenge of trying to standardize/simplify reporting how the peoples in a diverse world lived and died.



    Apache 2.4.27  PHP 7.19 MariaDB 10.2.8