View Single Post
Old 05-10-2010, 08:20 AM   #3
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 11,741
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
I don't use the server so don't have much incentive to follow through on this. That said, I suspect that the new virtual library feature (restrictions) would solve the problem/provide the requested functionality.

By setting a search restriction, the library display available would be limited to books that match the restriction. This will work as long as all the pathways from the server to the database go through ResultCache. They do if searching is supported.

Of course, it would be up to the user to determine what the search matches.

To make this work, one would need to:

1) add an option to library.server to provide the name of a saved search name to be used as the restriction.
2) change __init__ in library.server to call db.data.set_search_restriction with the saved search (set...('search:'+search_name)).
3) Change the configuration GUI so that the option can be specified there as well as on the command line.
chaley is offline   Reply With Quote