Biggest concern right now is records not showing up
I have really deep experience searching a few specific collections (I search these via dedicated bookmarks). Right now my biggest concern is things are not showing up that should be -- it seems possible that with the massive interface reengineering some logical conditions have been undermined. I am searching for, say, a death record and it doesn't show up in the results, but when I access the person on the FamilyTree that very death record from the collection I just searched is already attached. I search with a specific known death year from a gravestone and no death record shows up but when I remove the date and scroll through fifty or sixty weak matches there is the record near the bottom.
The whole assumption that "starting broad" is the best approach is really questionable in my opinion. I think this fundamental assumption is flawed and the cost is going to be (1) massively inefficient record retrieval (2) massive increase in erroneous record capture by inexperienced users with subsequent damage to the FamilyTree. I have a master's degree in information studies and coming up to thirty years experience as a genealogist, what has been done to the site appears to be a paradigm shift that may not be based on really practical, useable, principles. I wonder if you have brought in someone from a "management" field to rethink things. Hope you don't end up like General Motors...
Comments
-
I've been one of the biggest critics of the recent changes, but must be honest in saying that finding the expected results is now no worse for me (in most searches) than I had found previously.
Please provide an example (for privacy, change the name of your relative, by all means) so the engineers and ordinary users can test for themselves how difficult it is to make the specific searches (say for a death in a specified range of years) that you are having so much trouble with.
Removing details from the Search screen (e.g. remove any birth and marriage details when searching for a death) and filtering on "Type" and/or "Collection" is often necessary for me in getting the results I want.
1