Quote:
Originally Posted by un_pogaz
Yep, but that point only comes up if you specifically create a root element. So it's easy for the user to choose between having 2 lines or slightly renaming the root to make it a child depending on what they think is most relevant to this search.
foo , foo.search1 , foo.search2 => foo.All , foo.search1 , foo.search2
|
For one specific case, I have a 'Cleanup' search that encompasses several subsearches, which also execute subsearches — it's less cumbersome than all queries in one search, and lets me narrow down issues.
Code:
(search:"=Cleanup.Identifier Issues")
OR (search:"=Cleanup.Misc Issues")
OR (search:"=Cleanup.Missing Metadata")
If I wished to avoid double-entries, that means I couldn't just click on 'Cleanup' or 'Cleanup.Missing Metadata' and would have to instead check all of these individually for issues:
Cleanup.Identifier Issues.Convert ISBN-10s
Cleanup.Identifier Issues.Missing ao3: Identifier
Cleanup.Identifier Issues.Missing ffnet: identifier
Cleanup.Identifier Issues.Missing gutenberg: identifier
Cleanup.Identifier Issues.Missing odid: identifier
Cleanup.Identifier Issues.Missing standard: identifier
Cleanup.Misc Issues.Errored Fanfics
Cleanup.Misc Issues.Has Cleanup tag
Cleanup.Misc Issues.Has original_epub
Cleanup.Misc Issues.Incomplete fanfics
Cleanup.Misc Issues.Incorrect #kobopath
Cleanup.Misc Issues.No Formats
Cleanup.Missing Metadata.Missing Book Type
Cleanup.Missing Metadata.Missing Chapter Count
Cleanup.Missing Metadata.Missing Kobo Fields
Cleanup.Missing Metadata.Missing Language
Cleanup.Missing Metadata.Missing Page Count
Cleanup.Missing Metadata.Missing Tags