Search and System Glitches
Noticing lots of search errors and omissions. 1. Search parameters not working for location or age ranges. Example: Enter a foreign country and receive results for USA. Enter an age range and receive results for all ages.
2. Searches fail to display known ancestors in family trees. Example: If I enter my gg grandfather's name, birth date, location to perform a search, and his name on my Family Search tree never appears in search results, then using Family Search loses credibility re quality control, accuracy, and value.
3. Log in, perform search, review a family tree with similar name, then backtrack, click on "family tree" in header and display is family tree previously viewed during search - does not return to family tree established by user. Logging off and logging back in, clicking on tree again displays another tree, not user's tree.
4. What used to be two clicks to view data now takes five clicks. Very cumbersome.
Users (old and new) should have a more intuitive interface. The older version was more intuitive, logical and credible then newer version. If entering known data from a tree (i.e. first, last name, birth date, location) and the ancestor does not display in results, then search credibility is questionable.
Paul W ✭✭✭✭✭
I don't usually encounter these issues - as long as I check the "Exact" boxes that can be optionally added alongside names and places fields. Use of wildcards - especially by adding one at the end of a place name (e.g. "Sunderland*" instead of "Sunderland") helps produce something closer to the "anticipated" list of results, too.
However, one does have to discover many "search techniques" by experimenting with various "degrees" of data input: sometimes being too restrictive doesn't work so well, other times you do need to narrow down your search parameters (especially when using the "Exact" options).0
Paul W - Glad you are not encountering same issues. FYI, checking "Exact" box does not produce gg grandfather on search results. Even unchecking "Exact" box does not produce results. Still does not work if experimenting with first/last name and birth year and multiple other parameters. Unfortunately, same issue occurs on searches for other ancestors. Older version, no problem. New version, nothing.
Gordon Collett ✭✭✭✭✭
Unfortunately, the people in charge of programming the search algorithm can't fix anything without specific examples of unexpected behavior.
I don't know whether they are more likely to see such example here under Ideas or under the Search category of Q and A.
Regarding your concerns:
1) I assume this is under the Search Records function? If you post a specific search by posting the URL of the results screen and point out the problems in those results, anyone, including the search team, can click on the URL and see the search exactly as you entered it and see the same results. Then either someone can explain why you are seeing the results you are or the search team, I hope, can use it to tinker with the algorithm to improve it.
2) This is about the Find function under Family Tree, right? Here again, posting the results URL and your g-g- grandfather's Family Tree ID will be required for the search team to figure out why he is not first on the results list. A couple of years ago, I had entered a family in Family Tree and they refused to show up when using Find. I posted about it, they fixed something, and after that the routine worked as expected.
3) I think that is working as designed, which is based on the assumption that people generally want to stay where they are working, not continually be thrown back to the pedigree where they appear as the root person. Generally, the most efficient way to get back to the pedigree chart where you are the root person is to click on the Recents menu and click on the tree icon beside your name.
(Just as an aside here, because terminology is important, user's do not have trees here. You never leave "your tree" or go to "another user's tree." You are always just on a branch of the tree.
When first logging in, one does, however, usually end up back on the pedigree where one is the root person. I wonder if you log off and immediately log back in, the system does not register that you left? Have you tried logging out, waiting an hour, then logging back in? Does that bring up the tree view with you as the root person?
4) Agreed. I hope they continue to adjust the interface for the sake of efficiency of use.0