Forum

To my way of thinking, when I search for a recipe I (a) look first in indexed books and then (b) look in books that are not indexed. Because I don't need to search books with no recipes, I would like them to be filtered to fall into indexed books. All zero recipes are indexed.

When no recipes fall with the unindexed it makes it look like EYB has more work to do and makes me think I have more books to search manually than I do.

mjes,

I had exactly the same thought last night! :)

Having all the "no recipes" books fall under "indexed" makes a lot more sense to me. 

Cooking and food reference books are in the EYB Library with a No Recipes designation; the books without recipes that should not be added are non-cookery related books, which have sometimes been uploaded when someone tries to import their entire library, usually from another cataloging service such as Goodreads.

I'm going to be obnoxious and raise this issue again. Please realize that I am looking at it from the perspective of a system designer who has designed large systems from punch cards to web. From the perspective of the user, when they run a recipe search they get back two results:

1. a list of recipes that meet their search requirements


2. an implied list of books that have no recipes that meet their search requirements - it doesn't matter how many recipes the book has

To successfully search their library, they have two additional groups of books to consider:

1. books in EYB but not indexed - these can often be narrowed down by the book categories so one checks the indexes of only cookbooks likely to have the recipe (no need to search "no recipe" books - they have already been searched)


2. books not in EYB - here they're totally on their own and their way of shelfing books

From the point of view of a user, when they run a search and find no matching recipes in a book, it doesn't matter whether it is because no recipe matches or because there are no recipes. Either situation says don't consider the book further. A book "indexed" with no recipes behaves just like a book indexed with recipes. This means two things:

1. when applying filters books without recipes should fall into the indexed category


2. the multiple editions of books with no recipes should be linked so that all editions register as having no recipes (and so people don't request indexing on a book known to have no recipes).

Yes, from the point of view of the deisgner and the adminstrator of the system, no recipes means "don't waste your resources looking for an index - there isn't one" but from the point of view of the user, no recipes means "the system has searched all the recipes i.e. zero recipes".