Help get this topic noticed by sharing it on Twitter, Facebook, or email.

Missing Standardized Death / Burial Place Data Problem

When I get a red flag showing a missing standardized birth / christening event I find the bar below the event is yellow with a message to click to find a possible standard. However, this does not seem to apply to deaths and burials. Three times today I have found red flags to advise of missing standardized deaths or burials but, on checking, found the standard is already showing in green (as shown below).

I am following the same procedure for all types of event - in clicking outside the box so the chosen place can be displayed even though the "system" is supposed to see the (green) standard place. Why is there this inconsistency with different types of event?

Burials & Deaths show with warning flag:



Births & Baptisms inputted in same way (correctly) accepts entry:

2 people like
this idea
+1
Reply
  • I am still getting these messages for burials that ARE showing as standard against the event. As I say, in otherwise identical circumstances this is not happening for births & christenings.

    Would be grateful for confirmation that this is a bug.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • Could you provide some PIDs. Without those the engineers can't investigate.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • Can only find KJ56-R9F at present (the John Greengrass example illustrated above) and KL6-X6H. I have tried to replicate today without success.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • Found another today - L6SC-5F3. Again this is showing the standard place of burial (in green) when clicked on. So what is there to standardize?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • At last I HAVE found one for a christening - LK9C-941 - so maybe this is an intermittent fault and does apply to all events, rather than just burials / deaths - as had been my experience until a few minutes ago. All my previous Missing Standardized Christening Place messages had applied to where the Standard box was showing yellow.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • I'm seeing the message on at least 2 records - L6R4-ZY2 and L6R4-ZKT. Has this ever been resolved or explained?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • On L6R4-ZY2 you are seeing the message because there is no standard selected for the death place. The program is working as designed.



    To get rid of the red error icon, all you need to do is click on the yellow bar and select the correct standard.

    However, I assume you will want to correct the spelling of the city name and add the county and spell out New Jersey at the same time. So edit the place name, then pick the standard.

    Likewise, for L6R4-ZKT the program is working properly. The birth and death dates have never been assigned a standard.



    Since both years are entered just fine, just click on the yellow bar and pick a standard.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • Gordon

    Please remind me why I am having to change large numbers of records that are being displayed with a warning flag, as below. The standard is exactly as already displayed (Alnwick, Northumberland, England), so why am I having to waste my time by clicking on an identical place name? Is it connected to the details being brought over from nFS?

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • 2
    In the example you give of Thomas, the only thing I can say is that it looks like the last person to work on the place name on 11 Feb 2015 specifically choose "None of the Above" either on purpose or accidentally. I can't seen anything in the change log to say it could have been something else.

    I think 2015 would have been before the red icons were instituted.

    One thing that used to be a problem, and can sometimes still be triggered at times, is that if someone is a really good typist, enters the full place name quickly, then hits save without specifically clicking in the drop down menu, the standard bar with flash green which makes it look like your data entry is doing just fine in setting the standard. But when the edit box is reopened, the standard was never actually set and the bar is yellow. Maybe that is what happened with Thomas.

    If I remember right, hitting the tab key to move out of the place name field then using return to save would do this. You can tab out of the date field because that takes you to the place name field and the system does have the chance to set the date standard. Before the red icons, you would not have any warning this was happening unless you went back to check.
    • Gordon

      I have been trying to replicate this problem today, by deliberately not clicking on the standard (date or place name) and quickly hitting either the tab or enter keys. However, the date has still been accepted as standard and the place name standardised as the one shown at the top of the list. In the case of the date, it has not been visible on the screen when I (very quickly) hit the tab or enter keys.

      I have tested this both when adding a new person (say child) or directly on the person page and used both "Alnwick, Northumberland, England" and other place names in my entries.

      I'll take a further look at the dates when these inputs were made (to see if they were all around February 2015 time) as date of input may have some bearing on my receiving these messages for older inputs, but certainly not for ones being made right now.

      Thank you, Adrian and Tom for your contributors here.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • Thanks for your response, but I think the problem runs deeper than this. It seems to apply generally when the place name is specifically shown as above (Alnwick, Northumberland, England). I have had to change so many of these - and find I still have more to do.
    • view 3 more comments
    • I’m working from my iPad... Back a couple of years ago, I complained that the system labeled correct places as needing to be standardized when the place already met the standard.

      I got nowhere. The cleanup was left to us patrons, rather than run a program to check the entered place and if it agreed with the standard, set that standard.

      Alienating patrons is something that FamilySearch has been very good at in the past and continues to do.
    • I was pretty sure it was not just Alnwick this problem applied to - even in my experience. However, as there is a large branch in the tree where many of my ancestors and their extended families have Alnwick CM&Bs attached to them, this is the place where the problem has been very noticeable (and created a lot of work!) for me.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated

  • I was just fiddling around with this and figured out how to replicate the problem. Type out the place name, then while the drop down menu is open, click on the Save button. The bar turns green, but when you reopen the edit box, it is yellow.

    The reason I still think the particular example you provided was due to how the other contributor entered the birth place is based on the change log:



    When the birth information was first imported from New Family Search during the initial set up of Family Tree, no birth place was added. Then in 2015 the birth place was added manually. There is no evidence that it was added via a merge or via the source linker. There is no merge in the change log and the only birth source is the IGI source which does not include a birth place. Then the birth place was not touched until you standardized it.

    However, there could be multiple causes. Do you have a few other examples of people with this problem?
    • Thank you for this explanation and your experimenting, Gordon. Funnily enough, I decided to try to sort out the messy record of Thomas Stanley today and found his wife, Lucy Carter, had been entered as Lucy Williams. She is probably also the "Mary Carter" (as shown in an IGI record), entered as "another" wife of Thomas.

      Anyhow, Lucy Carter (LVD9-1YF) had a "Waltham on the Wolds, Leicestershire, England" birthplace displayed, which again was showing yellow, in spite of appearing perfectly okay as it was. I had just clicked on the same place name to turn it green when I came back here! Again, the change log shows an input of 11 Feb 2015.

      I'll try to find some more examples, but am pretty sure they will all relate to this patron's work on this and the wider Stanley-related family.
    • Interesting that Lucy was first created on that 11 Feb 2015 date by the same contributor. And you say you have noted a large number of individuals with the same lack of standard problem in this family.

      There is no notation that Lucy was created by a GEDCOM import but I have no idea when that notation in the reason statements was added. Was that something present from the start of Family Tree? Or was that added later, say in March 2015?

      Maybe there was a flaw in the GEDCOM import process at one point in which the standard was not added to the place name.

      Then there is the possibility that this was an early sync from a third party program into FamilyTree. Maybe the initial routines for syncing didn't handle the dual place name values well.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. happy, confident, thankful, excited kidding, amused, unsure, silly indifferent, undecided, unconcerned sad, anxious, confused, frustrated