Suggestion: Don't search the resource descriptions for words entered in the Library filter box
Don't search the resource descriptions for words entered in the Library filter box. It gives too many spurious hits. At least don't do it by default. Give us a tag to do it, though. There's too many irrelevant words in the resource descriptions.
Example:
MacBook Pro (2019), ThinkPad E540
Comments
-
Agreed. It took me a while to work out why some of the books where appearing in the Library after a search.
0 -
Agreed. It took me a while to work out why some of the books where appearing in the Library after a search.
Yeah, some of that comes from the subject field too, but I guess we can't exclude that.
MacBook Pro (2019), ThinkPad E540
0 -
I agree with Todd. There are too many unexpected matches and it just gets the user confused and frustrated so they'll give up.
Chris
0 -
But what if you want to find books on "historical background" -- which isn't in a title, but is in the Bible Knowledge Commentary's description?
I definitely get the point of too many hits, but we wanted to make sure we could help you find things... any ideas on how to keep both? Would it work if we could somehow rank higher hits from title, author, subject, and keep description hits, but lower on the list?
0 -
-
But what if you want to find books on "historical background" -- which isn't in a title, but is in the Bible Knowledge Commentary's description?
That seems a little random. Most commentaries give historical background. And most don't come up in a library search for historical background, and I wouldn't expect them to. If I type something in to the library box, I generally expect to find books whose focus is the what I typed in, not a book that might be tangentially applicable. Some of the descriptions go on and on, like Driver's Notes on Samuel and would pop up all the time.
I definitely get the point of too many hits, but we wanted to make sure we could help you find things... any ideas on how to keep both? Would it work if we could somehow rank higher hits from title, author, subject, and keep description hits, but lower on the list?
You could provide an advanced configuration to the library that had a checklist of things to search by default. Then we could turn off the stuff we don't want it to search. And we could turn it on when we needed to.
Plus you could add other library configs to it, like "only show resources rated higher than X stars" and "always sort by rank after a search". [Y][:D]
But I do agree that ranking based on hit location is a good idea.
MacBook Pro (2019), ThinkPad E540
0 -
But what if you want to find books on "historical background" -- which isn't in a title, but is in the Bible Knowledge Commentary's description?
I definitely get the point of too many hits, but we wanted to make sure we could help you find things... any ideas on how to keep both? Would it work if we could somehow rank higher hits from title, author, subject, and keep description hits, but lower on the list?
Why not make the description a searchable field, like "title:", why not have "description:"
If I want results sorted I want it to be by the field I have selected to sort by.
0 -
Philip;
V3 was pretty flexible in this regard.
I'd like to see this kind of specificity in v4
Robert Pavich
For help go to the Wiki: http://wiki.logos.com/Table_of_Contents__
0 -
Would it work if we could somehow rank higher hits from title, author, subject, and keep description hits, but lower on the list?
Fine with me. Keep description off the Library toolbar (keep it non-searchable) and rank its hits lowest.
Dave
===Windows 11 & Android 13
0 -
But what if you want to find books on "historical background" -- which isn't in a title, but is in the Bible Knowledge Commentary's description?
I definitely get the point of too many hits, but we wanted to make sure we could help you find things... any ideas on how to keep both? Would it work if we could somehow rank higher hits from title, author, subject, and keep description hits, but lower on the list?
I'd rather narrower search results than broader ones brought up by a search of description in most situations. Where I would more likely want to search description I would prefer to be able to search it as a field . Your suggestion though is a workable compromise. and would be appreciated if it can be done.
0
