@capink: Random thought -- does it make sense to give Single Field Edit the option to run over something other than the selection? I was thinking three options:
- Selection (what it does today).
- All books, ignoring the selection. What to do about VLs? Either use the current VL or ignore them?
- Books with ID in book_vars. This one I am not sure of. The idea is that a chain variables action does some computation and sets a book var for what it wants to change. Single field edit would loop over the books with any var set, calling the edit template.
The second is good for actions that want to do multiple things on many books. The third would be convenient for actions that want to do searches then compute results. For example, the second would solve @ownedbycats problem of modifying identifiers without selections. With the third my sample "average rating" function would become two actions with no selection modifiers.
What do you think?