Help get this topic noticed by sharing it on Twitter, Facebook, or email.
I’m very angry

EXTREME Fault/Flaw: All CUSTOM FACTS within OTHER INFORMATION Section prior to 5/6 September 2018 have been CHANGED to CUSTOM EVENTS.

"FamilySearch"

URGENT

----------

Please refer to:

Fault/Flaw: Certain FACTS within OTHER INFO Section are flawed/faulty: they, DO NOT recognise exact duplicates; &, OVERWRITE existing record

https://getsatisfaction.com/familysea...

----------

I have just identified another "Doozy" ( ie. an extreme fault/flaw ).

I thought I noticed this when I was "Testing" yesterday; but, I just considered it was my mind playing tricks on me ...

But ...

'NO' ...

I confirmed that it was actually happening.

I initially "Enter" and "Save" a "Customs Fact", no problems, all well and good.

Then later, I want to amend or update the information in the "Customs Fact".

No problems to "Assess" and "Edit" the "Custom Fact".

Make my required "Amendment" and "Save" - All good to far.

BUT ...

When "Saved" the "Custom Fact", right before my eyes, that "Custom Fact" literally CHANGES to a "Custom Event" !!!???

Never seen that one before.

A real FAULT/FLAW.

BUT ... wait ... it gets worse ...

I just checked a number of the individuals/person in "Family Tree" where I has added "Custom Facts" prior to 5/6 September 2018; and, 'lo and behold' ...

ALL those "Customs Facts" have been CHANGED to "Custom Events" !!!???

How did this oversight occur?

Why was this FAULT/FLAW that affects existing Data NOT identified; before, the update/release of 5/6 September 2018; and/or, following/after the update/release of 5/6 September 2018?

NO, NO, NO ... NOT ACCEPTABLE !!!

----------

What do we (the Users/Patrons) do?

Do we change the, now, "Customs Events" to "Custom Facts"?

OR,

Can you (ie. "FamilySearch") correct this FAULT/FLAW to those "Custom Facts" entered prior to 5/6 September 2018 - So, they remain exactly as entered prior to 5/6 September 2018, including the original 'Date' and 'User/Patron'.

----------

Submitted for your information and attention.

Brett
1 person likes
this idea
+1
Reply
  • This reply was removed on 2018-09-13.
    see the change log
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I’m very angry.
    Joe

    'Thank You' for responding to this post; and, the associated post.

    At first I thought the problem/issue of "Customs Fact[s]" CHANGING their "Type", from that of a "Customs Fact", to a that of a "Customs Event", when/after being "Edited", was not a major problem/issue; but, that was until I noticed that, in fact, ALL "Customs Fact[s]", that were "Entered" into "Family Tree", prior to the update/release of 5/6 September 2018, have had their "Type" CHANGED, to that of "Customs Event[s]".

    Initially, I thought that the latter was just an oversight or error; but, now, that I have time to think about it, I am leaning towards that that CHANGE to the "Type" of "Custom Fact[s]", that were "Entered" prior to the update/release of 5/6 September 2018, to the "Type" of "Customs Event[s]", was NOT an oversight or error; but, that, in fact, it was done by design.

    Question: Is this the case, that the "Type" of ALL "Customs Fact[s]", that were "Entered" prior to the update/release of 5/6 September 2018, did, in fact, have their "Type" CHANGED to that of "Customs Event[s]", was done by design?

    If, it is the case, that the "Type" of ALL "Customs Fact[s]", that were "Entered" prior to the update/release of 5/6 September 2018, did, in fact, have their "Type" CHANGED to "Custom Event[s]" was done by design; then, that was/this is NOT acceptable.

    In relation to the "Type" of ALL "Customs Fact[s]", that were "Entered" prior to the update/release of 5/6 September 2018, having their "Type" being CHANGED to that of "Customs Event[s]", to some Users/Patrons, this may not seem a problem/issue; but, to other Users/Patrons, like myself, this IS an major problem/issue.

    I have added "Custom Fact[s]", being things like - Twin and Cause of Death (for example) to many (countless) individuals/persons in "Family Tree", I am concerned; because, those "Custom Fact[s]" were just that "Custom Fact[s]. 'Yes', some (like the aforementioned examples) may have been associated with a "Custom Event"; and, are duly entered as such; but, those "Custom Fact[s]" that I entered, as such, were entered with the INTENDED "Type" (ie. format) of a "Customs Fact"; NOT, a "Customs Event".

    If, it was the case, that the "Type" of ALL "Customs Fact[s]", that were "Entered" prior to the update/release of 5/6 September 2018, did, in fact, have their "Type" CHANGED to "Custom Event[s]" was done by design; then, I do not understand the reasoning/motive behind such, as those CHANGED "Custom Fact[s]" DO NOT have a 'Date' or a 'Place' and would NOT appear on the "Time Line". Unless it was the intent, that at some time later in the future, that some other User/Patron, may come along and add a 'Date' and/or a 'Place' to such "Custom Event[s]" that do not have a 'Date' and/or a 'Place', so that they appear on the 'Time Line' - if such was the intent; then, this was/is NOT acceptable.

    Whatever the reasoning/motive, whether by design or oversight/error, it was/it NOT acceptable, for "Customs Fact[s]", that were "Entered" prior to the update/release of 5/6 September 2018, to have their "Type" being CHANGED to that of "Customs Event[s]".

    I am very concerned with what has happened in relation to this matter.

    I am equally concerned as what will happen with all those "Customs Fact[s]", that were "Entered" prior to the update/release of 5/6 September 2018, that have had their "Type" being CHANGED to that of "Customs Event[s]".

    If there is an intention for all those "Customs Fact[s]", that were "Entered" prior to the update/release of 5/6 September 2018, that have had their "Type" being CHANGED to that of "Customs Event[s]", to be returned/reverted to the "Type" of "Customs Fact[s]"; then, my concern is that they will NOT be returned/reverted with the original 'Date' and 'UserID' of the relevant User/Patron; as, was the case with the fiasco of the "Deletion" / "Removal" of the "Alternate Names" that were returned/reverted, not that long ago.

    I hereby formally request and (to some degree) insist that, if there is an intention for all those "Customs Fact[s]", that were "Entered" prior to the update/release of 5/6 September 2018, that have had their "Type" being CHANGED to that of "Customs Event[s]", to be returned/reverted to the "Type" of "Customs Fact[s]"; then, that MUST be done so that the original 'Date' and 'UserID' of the relevant User/Patron is applied to those records; and, NOT, return/reverted with the 'Date' of that of the return/reversion or the 'UserID' of "FamilySearch".

    Could, you; or, the relevant Manager responsible, please keep us abreast of the developments in this matter, that I have raised in/by this post.

    'Thank You' in advance.

    Submitted for you information and consideration.

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

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

  • I’m still very angry. But, now hopeful.
    Joe

    It would appear, that the first part of my post, has been addressed/fixed.

    I have just "Accessed"; "Amended"; plus, "Saved", a "Custom Fact"; and, that "Customs Fact" that was "Saved" stayed/remained as a "Custom Fact"; and, did not "Change" its "Type" to a "Custom Event".

    'Thank You' personally for you assistance in that matter; and, please 'Thank' all the relevant "Team" in "FamilySearch" who were responsible for that "Fix" in that matter being so swift.

    I only hope the second part my post, about ALL those "Customs Facts" that where added prior to 5/6 September 2018 having been CHANGED to "Custom Events", can be addressed and fix, ASAP.

    I do not know whether to go through all the countless individuals/person in "Family Tree", with whom I am associated, who I have added "Custom "Fact[s]", prior to 5/6 September 2018; and, address/fix the problem/issue myself; or, wait!?

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

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

  • Brett, what are those PIDs where they were corrupted to Custom Event?
     The bug may be fixed but need to look at it there was data corruption that has lingered. Thanks
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Ron Tanner in one of his Facebook Q&A sessions actually talked about lumping various Other Information entries together. What we now see is a result of that and in my opinion, it is a mistake. Every Residence that I enter has at least one source behind it. Because we cannot enter sources against any "Other Information" entry, I have had to resort to using either the reason statement or the Description field (on Residence) to indicate where the information came from. In some cases, I indicate the source, such as "1905 Kansas State Census, details from the enumeration pages" in the reason statement. It would be so much easier to actually attach sources to their events.

    Eventually when FamilySearch eventually adds the feature, the sources cannot be lumped together as they are now. Open an event and look at the See All Changes filter in the change log. The filter also has all the same event types lumped together, including those that are "Other Event."

    That is now a problem and going to be a bigger problem when sources are attached to individual events.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • I’m still very angry. But, now hopeful.
    Joe

    Sorry for the delay in my response ...

    I just woke up to a new day, over this side of the World, from "Down Under"; and, had to undertake my morning ablutions and chores; plus, check on a response from a User/Patron with whom I had "Messaged" yesterday (last night/this morning) - they had added a Daughter to one of the individuals/persons with whom I am associated. The problem/issue was that this so called "Daughter" was born in the USA some 45 years prior to his Marriage in England. I have not yet confirmed; but, have estimated that that she was born about ±25 years prior to his birth. I was lucky to get a "Message" response back so quickly; but, was so concerned to see the dreaded six letter word ... GEDCOM. Ever so luckily, no serious damage done; and, a very easy fix.

    =====

    As previously advised ...

    It would appear, that the first part of my post, has been addressed/fixed.

    I have just "Accessed"; "Amended"; plus, "Saved", a "Custom Fact"; and, that "Customs Fact" that was "Saved" stayed/remained as a "Custom Fact"; and, did not "Change" its "Type" to a "Custom Event".

    'Thank You' personally for you assistance in that matter; and, please 'Thank' all the relevant "Team" in "FamilySearch" who were responsible for that "Fix" in that matter being so swift.

    I only hope the second part my post, about ALL those "Customs Facts" that where added prior to 5/6 September 2018 having been CHANGED to "Custom Events", can be addressed and fix, ASAP.

    I do not know whether to go through all the countless individuals/person in "Family Tree", with whom I am associated, who I have added "Custom "Fact[s]", prior to 5/6 September 2018; and, address/fix the problem/issue myself; or, wait!?

    =====

    BUT ...

    I have checked a few ...

    There has been NO fix/correction to the countless "Customs Facts" that where added prior to 5/6 September 2018 having been CHANGED to "Custom Events".

    Those original "Custom Facts" are still appearing as "Customs Events".

    =====

    I know that the "Fix /"Correction" for the problem/issue of those "Customs Facts" that where added prior to 5/6 September 2018 having been CHANGED to "Custom Events" is a much bigger matter to address.

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

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

  • Brett, thanks for confirming that they aren't fixed. They are unlikely to get fixed unless the engineers can investigate the bad data. Can you provide the PIDs of these Persons that have the problem?
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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

  • Brett, has this been resolved?

    I just did a quick test and entered a Custom Fact.

    It recorded as a Custom Fact, so I do not believe this is a problem at this point.

    However, when the new interface was rolled into production, some "custom facts" may not have *stayed* as custom facts.

    I also checked one of my ancestors and the "custom fact" is displayed as a custom fact, so this appears to have been fixed, as Joe indicated.
  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

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