Occasionally, author entries are created by accident. They can't be deleted, but can be marked as duplicates, or edited and re-used. In the latter case, they are left blank until the next time we'd add an author. We don't want them in the search results in the meantime.
Currently, they show up at least when browsing by author:
https://librivox.org/search?primary_key=0&search_category=author&search_page=1&search_form=get_results&search_order=alpha
Code-wise:
The unwanted entries will have authors.confirmed=0, and will not be assigned as author or translator of any project (or section in a Collection/is_compilation=1 project).
Assuming the above search gets its results from search_table, we might just want to exclude authors matching those criteria from that table whenever it gets re-populated. Not sure whether an author should be excluded if BOTH conditions are true, or just one.
Occasionally, author entries are created by accident. They can't be deleted, but can be marked as duplicates, or edited and re-used. In the latter case, they are left blank until the next time we'd add an author. We don't want them in the search results in the meantime.
Currently, they show up at least when browsing by author:
https://librivox.org/search?primary_key=0&search_category=author&search_page=1&search_form=get_results&search_order=alpha
Code-wise:
The unwanted entries will have
authors.confirmed=0, and will not be assigned as author or translator of any project (or section in a Collection/is_compilation=1project).Assuming the above search gets its results from
search_table, we might just want to exclude authors matching those criteria from that table whenever it gets re-populated. Not sure whether an author should be excluded if BOTH conditions are true, or just one.