Do not require reason statement for creating a person if Date is added for death field

LegacyUser

Jordi Kloosterboer said: I used to not need to require a reason for adding someone if I provided a death date. Now I need to. I suggest not needing this, but if you guys want to keep this, I would like to know why. Obviously I think they are dead if I have a death date. For now I will add a character to the reason.

LegacyUser

Jordi Kloosterboer said: This is particular to the source adder screen.

LegacyUser

Don M Thomas said: I have been having problems with this myself. I fill in all spaces and still I can not get the "Create New Person" button to turn blue. Only way I can get the "Create New Person" button to turn blue, is to put something in the reason box. Putting death date or place should be all that is needed.

LegacyUser

Amy Archibald said: I put in the reason field how I know they are deceased. Some examples I use:

Headstone
Obituary
Death record

LegacyUser

Juli said: I posted about this back in November. (Naturally I can't get GetSat to cough it up.) I've resorted to putting in a period -- anything else (including something like "death record") shows up as redundant nonsense on the profile page.

LegacyUser

Paul said: I believe I used to get around this by double-clicking on "Deceased", but maybe this applied to different circumstances. There appeared to be no way around it when I was working on similar examples (to that illustrated) yesterday. Like Juli, I just input a dot (period) to save wasting my time with an unnecessary reason statement.

LegacyUser

Jordi Kloosterboer said: For additional information, when I add a character like a period, I can create the new person (the button turns blue) and when I backspace that character, the button turns gray again. The programming wants me to put in reason for death which is redundant and silly in my honest opinion and some of your opinions too it seems. Because this person was born between 110 years and 0 years ago, it is logical to add a reason of death if no death date is provided so I understand that. (I assume people born 110 years ago are dead because VERY few people have passed that age in modern times and therefore no reason statement should be required for them or at least past 120 years ago or child was born that long ago etc.)

LegacyUser

Juli said: Adding someone via Source Linker requires a reason for death even if the birthdate you just finished entering was 250 effing years ago. The requirement persists despite entering the death date, on the day following birth.

It's like SourceLinker's Add Person function firmly believes in vampires.

LegacyUser

Jordi Kloosterboer said: haha yeah

LegacyUser

joe martel said: This speed bump was added because a number of users here on GetSat and elsewhere complained that their living relatives were being added as deceased, thus exposing living person information. Since adding the Reason requirement I haven't heard of any such privacy violations happening. So the product errs on the side of being more protective of potential privacy exposure.

That being said, it was just easier to code and always require a reason statement for the user to declare them as dead when adding that new person. If forced users to slow down and actually look at the data (maybe not enough for some users...). Yes the death event date seems to be a dead giveaway, but we know indexes can be wrong and that 1794 was supposed to be 1974. I can see both requests (not requiring a reason if death or born >110yrs ago, or always requiring by looking harder and declaring what you see in the Reason statement. Amy's post above gives a good approach. 

LegacyUser

Amy Archibald said: In 2019, I made 25 dead to living case requests.

One user had created 9 of the dead records (of living people) and I tried contacting the other user. I gave them one month and didn't hear from them and so I completed a case for each of the people they had made deceased who were living.

I believe that taking a quick moment to record why the person you are entering as deceased is important. Because on each of the 25 that I reported last year, not ONE had any kind of note in that field and they were all created via SourceLinker.

LegacyUser

Adrian Bruce said: Juli - I thought you did Hungarian, not Transylvanian? (Sorry - couldn't resist!)

LegacyUser

David Newton said: The problem with that joke is that Transylvania was part of Hungary for many hundreds of years!

LegacyUser

Juli said: Vampires were invented by an Englishman. He chose to put them in Transylvania because it sounded exotic and foreign.
There is nothing even remotely like vampires in Transylvanian folk tales or mythology.
(And yes, as David says, Transylvania was part of Hungary before the now-century-old travesty known as the Treaty of Versailles. Despite the government's best attempts at Romanianization, you can still basically think of Transylvania as the Hungarian-speaking half of Romania.)

LegacyUser

Adrian Bruce said: Now the Hungarian speaking bit I did not know....

LegacyUser

Jordi Kloosterboer said: I guess it is good for slowing down people so they do not add living people. I will continue to just put a character in it because I can't be bothered to add a reason statement:P

LegacyUser

Ron Tanner said: The expectation is that since you are creating a new person and there is no evidence of death on the indexed record, then you should explain why you would be marking this person as deceased with no record of that event.

LegacyUser

Jordi Kloosterboer said: Ah ok that makes sense.

LegacyUser

Ken G Moyer said: I have been bothered by this problem for some time, especially when adding children. Starting from the top of the 'Add' form and entering the info as I go down the page and selecting 'Living' one gets a page change that limits more info, BUT if I select 'Deceased' I get a different page setup whereby I can add dates, Father, Mother etc, but before I select 'Add' I change Deceased back to Living. Seems like there is two forms mingled together. It's a pain in the you know what to have to remember to switch back to Living, and if I forget to change it I have to open that persons home page and correct it.

LegacyUser

Juli said: IMNSHO, if they're living, you shouldn't be creating profiles for them. Keep track of them in your offline genealogy program, if you want, but don't put information about living people online. One misclick and you've revealed private data for all the world to see. Yes, you can fix it on this site if you discover your mistake, but you can't fix it in all the places that copied it in the meantime.