Boolean tag "NOT" query study inspector results not adding up#493

I have a nest where we screened in two batches, and the first batch is tagged “previously screened”. I need to filter out these studies to QC the screening on the newer studies, but when I use the Boolean tag filter for NOT “previously screened”, no studies come up (733/1503 records show up as tagged “previously screened). I’ve added a new tag in case there was something about the way “previously screened” was applied, but there’s no change. I also tested the Boolean NOT query in a test nest, and the number of studies pulled up there wasn’t correct either (240 studies found with the NOT “Registry” query, but only 23/5242 studies tagged “Registry”. It seems like maybe the Boolean NOT query is only looking at studies that have at least one tag? I haven’t verified that theory, though.

Project nest: https://nested-knowledge.com/gather/inspector/3572
Test nest: https://nested-knowledge.com/gather/inspector/3118

Let me know if there’s any other info that would be helpful or if I’m just going crazy! I’ve used the Boolean NOT query successfully in other nests, but only in included/tagged studies for end stage QC. I need to QC the screening shortly, but I think I have a strategy to get around this and ID the studies that need to be QC’d by deleting the studies that were previously screened in a copy of the nest, tagging the rest, and then importing tags to the original nest.

Thanks!
Erin

HI Erin - Good inference, our tag query only operates on studies with 1 or more tags applied. So, your query NOT "previously screened actually reads more like [has one or more tags applied] AND NOT "previously screened".

When I consider your use case, this really sucks; for more vanilla use cases, this isn’t an issue, as typically, within included studies, every record has at least 1 tag.

• As a cruddy workaround, you can add a dummy tag to all studies in your nest using a bulk action. Then run your NOT query
• We’ll update the our tag query library (open source here) so that NOT queries may be evaluated against a dataset that includes records without a tag.

Thanks Karl! Your workaround of adding a dummy tag is easy to implement, so I’ll be able to do what I want to do on this project. I’ve been working in Distiller for another client project and it’s made me really appreciate the flexibility has NK that allows you to search and filter studies for exploration and admin purposes, in addition to standard review activities!

It turns out we already implemented this in the core library, just needed to plug into it correctly. Look for this to be fixed in the next release!

Awesome, thanks Karl!

Fixed in 1.54.0. Thanks for reporting!