Let's be more sensitive with mass emails
I was going through my email and found this one.
Yes, it is history and I know it was done. But being Japanese myself having a email like this, i find it very insensitive. Because family search is for everyone I think whatever team that is in charge of mass emails should think what the race will feel (especially war related items).
Comments
-
It seems like the photo isn't working. The email I got says "Your great grandmother was living when pearl harbor was attacked. Our Family is Japanese
3 -
It is disappointing that you do not appear to have received a response on this matter from a FamilySearch employee - unless they have sent you a private message, of which we would not be aware.
I suppose this is a tricky issue, as these messages are almost certainly computer-generated, so it has not been the action of an insensitive individual that has caused you to receive this. However, perhaps "FamilySearch" might want to give further consideration to the nature of events it shares with its users.
Recently, there was a complaint from another user, who was unhappy about details of Donald Trump's inauguration appearing on his timeline in Family Tree. This prompted me to look at historical events that had been added to my relatives' timelines. They appeared to be quite random, although I found they did generally relate to the country in which that person resided. Nevertheless, I did worry about where the line was being drawn between events that could be considered as "plain historical" ones and others that did involve political (even military) actions / events, the notification of which might cause some upset to certain individuals. This would especially apply, of course, to those who had been personally affected by the reported event.
In summary, I would hope the FamilySearch sections responsible for the content of such emails (or programming similar events that end up on Family Tree timelines) will give a little more thought to including items of a political nature, or that might prove upsetting for some users to read. I was born on the same day as an evil dictator and would be particularly upset at getting that reminder from FamilySearch!
0 -
I just came here to comment on a similar thing. Having the only historical item on a living Black American's timeline be the ignominious Donald Trump's inauguration is, frankly, odious. If every president were there, it would be different. But having it be the only one? Nope nope nope. I expect much better of FamilySearch.
0 -
"Be ye not offended."
(A general suggestion for many of these similar comments - and commenters.)
0 -
Good advice, but sometimes easier said than done!
A little more consideration as to which events to include might go a long way in preventing any offence, however. Surely there must be some way of excluding anything relating to war and politics, which are bound to be sensitive subjects for many individuals?
0 -
I believe Historical Events in a persons' Time Line are curated by FamilySearch. But also they can be enabled/disabled per each person profile (see Time Line> Show options below):
So if one does not want these items to appear - there is a method for their removal. I think a larger point is that one can create/Add Custom Events as one wishes. So for example one could copy/Add any desired Historical Events as Custom Events and turn off Historical Events. I do note that most items can be Edited but Historical Events is not editable (thus indicating FamilySearch curation). Yes perhaps more discretion could be used in Historical Events - as could their removal if offense is taken (grumble ... ).
The Historical Events: Roe Vs. Wade is listed - noting its highly controversial nature - also listed is the assasination of Sen. Robert F. Kennedy - so I don't think FamilySearch is avoiding controversial Events. Perhaps that is somewhat of the point being made - events are events - whether controversial or not. But I guess to reiterate the point I am mentioning here - these items can be disabled. In fact the only items that cannot be disabled on a person's Time Line is Vital Events (BMD) - so if one doesn't want to view any other events - they can be disabled.
Perhaps this idea could be edited to include a request for global Time Line edits (so the need to disable per person was not necessary)? Of course there are options to disable emails/notifications as well in Profile Settings> Notifications OR under the bell icon (notifications - next to profile icon) you can also Mute individual notifications. It seems like many of these notifications are removed after a short campaign period (for example - I no longer see some notices).
0 -
It's not the first time I've seen this complaint on this forum. The only reason I can see for including the Presidential inauguration of 2017 is that between 2017 and 2021 it was the most recent inauguration to have occurred. But that has no longer been the case since January 2021, and in any case the inclusion of recent politicians is always going to be controversial.
0 -
These historical factoids appear also on the public Ancestors pages. Some combinations I've seen there have been quite, er, unfortunate.
Apparently the factoids were purchased as a set from a vendor and are more or less randomly selected based on generic criteria such as dates and places. It is a lot like a Chinese restaurant fortune cookie: you take your chances.
As a contributor to many profiles I try to retain a sense of humor about the unfortunate combinations and not feel they reflect badly on me personally.
0 -
All
Just my thoughts ...
The "World Events" (ie. "Historical Events"), in BOTH,
(1) the 'Time-Line', of an individual/person, in the "Family Tree" Part, of Familysearch';
AND, ...
(2) the "Discovery Pages", for an individual/person in the more RECENT "Ancestors.FamilySearch" [ .org ] Part, of 'FamilySearch',
is BOTH, "Controversial"; and, "Divisive' ...
Although, originally well intentioned, meant to be, additional interesting facts, about "World Events" (ie. "Historical Events"), during an Ancestor's life time, the perception of ANY "World Event" (ie. "Historical Event"), is in the 'eye of the beholder' ...
In other words, a (ie. the SAME) "World Event" (ie. "Historical Event"), may well, be quite acceptable/appreciated by one particular User/Patron; but, may be totally, unacceptable/unappreciated, by another User/Patron.
Even people, in the same "Country"; and, in the same "Culture", CANNOT always agree ...
That is just 'human nature' ...
EVEREYONE has their own perception; as, to what, is; or, is not, an acceptable/appreciated "World Event" (ie. "Historical Event").
And, the OTHER problem/issue, that exists is ...
What should; and, what should NOT, be included, in "List", that appears for "World Events" (ie. "Historical Events").
That can be very subjective; and, who (in 'FamilySearch', in this case) gets to make the "Decision".
Personally, due to the 'sensitivities' (and, 'perceptions'), of BOTH,
(1) ALL the VARIOUS Users/Patrons, of the "Family Tree" Part, of 'FamilySearch', from ALL around the World;
AND, ...
(2) EVERYONE, in the World, that can and will access, the "Discovery Pages", for an individual/person, in the more RECENT "Ancestors.FamilySearch" [ .org ] Part, of 'FamilySearch' ...
There is an EASY fix ...
I would humbly suggest, that 'FamilySearch' would be, 'better off', simply, "Removing"; and, dispensing with, the "World Events" (ie. "Historical Events"), altogether, from BOTH,
(1) the 'Time-Line', of an individual/person, in the "Family Tree" Part, of FamilySearch';
AND, ...
(2) the "Discovery Pages", for an individual/person in the more RECENT "Ancestors.FamilySearch" [ .org ] Part, of 'FamilySearch'.
Doing so, would STOP all the, "Controversy"; and, "Divisiveness", regarding "World Events" (ie. "Historical Events") ...
And, such, would ALSO be better in keeping, with the ethos of 'FamilySearch' ...
Just my thoughts.
Brett
0 -
Hello @Nezumi,
Thank you for reporting this and providing feedback on how we can be more sensitive. I have passed this feedback on to our marketing team to review.
Best,
Mark
3 -
In future, if I see unfortunate combinations I'll try to remember to share a screenshot here.
1
