Make "Passages" dropdown restrict Fuzzy Search results
Rosie Perera
Member Posts: 26,202 ✭✭✭✭✭
If I want to search for something only in Paul's letters, for example, and I'm not sure of the wording, I want to rely on the Fuzzy Search results, but don't want to have to page through all hits throughout the entire Bible.
Please make the Fuzzy Search results pay attention to the passage restriction.
Please make the Fuzzy Search results pay attention to the passage restriction.
16
Comments
-
You need an option to remove the Apocrypha from the Fuzzy Bible Search bar. I use that feature a lot, and it's a pain to have to scroll past Sirach and Tobit to get to the actual Scriptures.1
-
Shouldn’t have to vote on this it should just be done.0
-
@andrewmckenzie-70 Well, it was pointed out as a problem as far back as 2017, and Andrew Batishko created a case for it on their internal tracking system, but evidently that wasn't enough, as it's now nearly four years later. So we need to all pile on and vote for this to raise the priority in their minds.
https://community.logos.com/forums/t/148370.aspx0 -
@Rosie And there lies the problem FL just don’t get it when they should, we shouldn’t have to vote on something so obvious in order to get it fixed. They hide behind saying it wasn’t in the design instead of admitting their design was floored and fixing it.0
-
@andrewmckenzie-70 Problem is even if something is "obvious" it might be non-trivial to fix, and they have hundreds of things they want to fix but need to prioritize them. I wish they wouldn't rush to add so many new features before fixing things like this, though, especially since it was pointed out to them so long ago.0
-
@andrewmckenzie-70 If almost no one cares, then FL has no good reason to fix it. Voting for this suggestion tells them about how many people care.0
-
@SineNomine saying something should simply be fixed it has been brought to FL attentions without the need to wait till it reaches some undisclosed tipping point is not caring, it’s the opposite. It’s saying let’s cut out the delay FL has inserted into the process so they can put things off and instead just fix it. A search without the ability to filter the range is poor design on FL’s behalf - it’s their stuff up and we should not have to wait for a vote to show we care fir them to fix their stuff up, they put together an inadequate specification for this function in design phase and they should go back and do the job properly. If I get something wrong at work I don’t wait for enough people to vote on how much they care about it before I put my hand up and say I got it wrong and fix it. I act immediately I know I got it wrong. Someone at FL got it wrong and we are allowing them to not take responsibility for that fact and letting them hide behind a popular ‘care factor, vote. That is not good enough IMHO.0
-
Allow the software to exclude the apocrypha in returning search results (fuzzy or anywhere else)1
