Kiwitrees on Twitter

    500, close, message contactform, ID facts, 5.6, calendar.php issue, simpl_grey, seo, pages, blank screem, access roles, white screen, ASSO, notes, event, permissions, fancy image bar, survey, cookie, json, lists individuals families, census assistant, googlemap. modified, 3.2.3, Google Maps, Php 7.1, individual resource, datatables, kiwitrees theme, add missing death, dropbox. token, last change date, CREM, bug, Search and replace, internal messaging, CHR, language, footer, PHP, html, widget, simpl_research, resources, search, 3.2.1, reports, birth, php 5.6, googlemaps, check, inactive, 3.3.1, family, prefix, custom text, 3.3.0, 3.0.0 widgets, edit, 3.0.0. setup


    1642 posts

    Well we are both working from recollection so I will look into it in the next few days.

    Regarding census entries, yes I agree. Over the years looking at census (and other documents) I have been constantly astounded at the range of “discrepancies”. Not all are accidental either. I’ve seen many odd entries clearly designed to cover various “indiscretions”.
    In such cases I always a) transcribe everything EXACTLY as I find it on the original document; and b) by adding explanatory notes Occasionally I also add full or partial (cropped) images to emphasize the point.

    My personal kiwitrees site is