Efficiency of user experience
So I have 5 unrelated ideas that would save time:
1) let living people (obviously that I created) show up in descendants with tasks
2) in the my contributions section and the living people subsection of the app, please let the blue research hint show up. Not everybody that was born 109 years ago is alive and having the blue button show up would help me more quickly move these people from living to dead.
3) when attaching records in the app, I love the “apply” button. BUT separate “apply date” and “apply place” buttons would be even more helpful. For example, consider a person who had July 6, 1998 as their birthday but no place and a record that says 1998 with a very detailed location. The apply button overwrites the detailed date with 1998. It would allow me to more easily retain all the information if I could have this separate button,
4) somehow allow me to see the relationship between two dead people like you allow me to easily view my closest relationship.
5) allow me to search for grandchildren. For example, I attach a record to person A who has 13 children and the record has a grandchild on it. Rather than having to open all 13 children and see who the grandchild belongs to...let me say I want to search for a grandchild named X that is within 3 generations below person A.
Comments
-
Spencer
.
I am just another User/Patron, like yourself ...
.
Question: Are you referring to using, the "Mobile" Application version; or, the Computer (Web) version, of "Family Tree" of 'FamilySearch'?
.
The reason for my question is that you use the "app"; and, the "Mobile" Application; or, the Computer (Web), versions, look and feel quite DIFFERENT.
.
Just some comments ... referencing the Computer (Web) version ( ONLY ) ...
.
[ In Parts ... I had to break it up into parts (too big for one 'comment') ]
.
[ Part 1 ]
.
Idea 1
.
Much (and, in fact, often) requested ...
Unfortunately, easier "Said", than "Done".
.
Briefly ...
.
There is CURRENTLY no mechanism in "Family Tree" of 'FamilySearch' for Users/Patrons, to "Share"; or, "give permission" to "Share", the "Living" individuals/persons in their own "Private Spaces" with/between other/another User(s)/Patron(s).
.
There are a MYRIAD of "Privacy" Laws within the MANY various Countries and Unions throughout the World - it is a nightmare to negotiate.
.
"Family Tree" of 'FamilySearch' is used by many Users/Patrons from the MANY various Countries and Unions throughout the World; and, as such, must adhere to the MYRIAD of "Privacy" Laws throughout the World.
.
Hence, "Privacy" is one of the reasons that we cannot "Share" the "Living" individuals/persons in our own "Private Spaces" - it is NOT the ONLY reason; but, certainly has a bearing on the matter.
.
Another factor is that such would have to be 'Coded'/'Programmed' into the Programme that is "Family Tree" of 'FamilySearch'.
.
I believe that 'FamilySearch' is EXPLORING avenues with regard to, "Inheritance"; and/or, "Bequeathing", of the "Living" individuals/persons (and, most likely, the "Memories" of such) in the "Private Spaces", of a recently deceased Family member, to an immediate Family member.
.
And, I also believe that 'FamilySearch' is EXPLORING much MORE in regard to "Living" individuals/persons in our "Private Spaces" ...
.
Something that WILL take some time, 'make no bones' about that ...
.
[ Continued in Part 2 ]
.
Brett
.
0 -
Spencer
.
[ Part 2 ... continued from Part 1 ]
.
Idea 2
.
That "Contributions" Section is only a recent addition to "Family Tree" of 'FamilySearch'; and, as such, not a bad idea, in fact, a good idea.
.
Idea 3
.
IF, you are suggesting to, SPLITING, the 'Date'; and, the 'Place', fields, for "Events", while "Attaching" a "Source"; THEN, 'No', they should stay together; as, we have an "option" to "Change" the 'Details' for both, while attaching - if needs be.
.
I do not understand what you are getting at!?
.
[ Continued in Part 3 ]
.
Just my thoughts.
.
Brett
.
0 -
Spencer
.
[ Part 3 ... continued from Part 2 ]
.
Idea 4
.
NOT necessary ...
.
This functionality ALREADY exists in one of the "Third Party" Applications that is "Certified" to work with 'FamilySearch'.
.
Can I humbly suggest that you could try (BYU) "RelativeFinder" ...
.
(BYU) "RelativeFinder" digs (pun intended) a lot DEEPER in "Family Tree" of 'FamilySearch', than 'FamilySearch' does.
.
(BYU) "RelativeFinder" is one of the "Third Party" Applications that "Certified" to work with "Family Tree" of 'FamilySearch'.
.
BYU = Brigham Young University, in Provo, Utah, USA (ie. the Church University).
.
From the "Family History Technology Laboratory", of the "Computer Science" Department.
.
Here is direct link to "RelativeFibder"
https://www.relativefinder.org/#/main
.
.
"RelativeFinder" has many 'Bells and Whistles', that you might find useful.
.
Apart from your links/connections to, "Famous People"; and, "Others" ...
.
(BYU) "RelativeFinder" has some interesting options ...
.
There is an option to see if there is a 'Connection' between yourself and a "Deceased" individual/person in "Family Tree" of 'FamilySearch'.
.
.
There is an option to see if there is a 'Connection' between two (x2) "Deceased" individuals/person in "Family Tree" of 'FamilySearch'
.
.
There is an option to see if there is a 'Connection' between ("Living" - Users/Patrons) Friends in "Family Tree" of 'FamilySearch'.
.
.
Give them a go ...
.
And, there are many other 'Bells and Whistles' that you might find useful in "RelativeFinder".
.
Magic.
.
Enjoy.
.
Idea 5
.
Question(s):
.
Are you referring to "searching" within YOUR "Ancestral" lines in "Family Tree" of 'FamilySearch'?
.
Or, are you referring to "searching" within the Records in 'FamilySearch'.
.
Just my thoughts.
.
Brett
.
ps: 'The End'.
.
0 -
I have read your responses. Thank you for your thoughts. I would like to clarify some of my suggestions.
All of my comments relate to the app. The app (I am guessing) is where all the action will be in the future as far as volume of user interaction is concerned. I honestly think the app has far more functionality than the website.
Idea 1. I am not suggesting living people showing up in other peoples descendants with tasks, I just want it to show up in my own. I don't think it does currently but maybe I am wrong. I don't think this violates any of the privacy issues discussed.
Idea 3. I understand why there might be some concern about splitting dates and places from records but I believe a thoughtful programmer plus a thoughtful group of users could resolve any of those concerns. All my points are about efficiency. By efficiency I mean allowing the tree to grow accurately as much as possible per unit of users time invested in the app. In the following scenario allowin a user to CHOOSE (KEYWORD CHOOSE) to apply a date, a place, or both to a person is definitely more efficient. Consider this example:
Person A has a birth date recorded (and backed up by a record) on January 1 1933 but there is no birth place. Then a Census comes along and says this person was born on 1932 in a specific place. I believe it is best to keep the most specific but still accurate information possible. The birthdate january 1 1933 is more accurate and specific than the estimated census date but the birthplace on the census is better than the specific place. A thoughtful user already has the option of putting this information in. I am only advocating changing HOW a thoughtful user can change dates and places. An "APPLY DATE" and "APPLY PLACE" button allow me to not have to manually edit anything and keep the best information available. Users can already split dates. I just want it to allow me to do so (when appropriate) more quickly.
Idea 4. I am glad to hear that 3rd party applications allow this but opening up multiple applications certified or not is much slower. The tree grows fastest when fewer clicks allow the user to make decisions. Allowing me to use an easy to create button within the family search app is more efficient. Which in my case is the only goal.
Idea 5. I want to search within any family line I specify. I want to put the ancestor or descendant in and then search for a name within 2 or 3 generations up or down.
0 -
Regarding Idea #5...in the web version...use the descendancy view for the tree instead of landscape. Change the number of generations you'd like to see. It is not available on the app (yet?). Love using this for finding hints, things that need standardizing, etc.
0
.
.
.
.