How to display included/excluded applied filters?

Question

I am building something that allows users to search (for things like words, hashtags, etc) and apply this search to a report that they have built off of twitter posts. So for example, a user that works at Nike may want to search their report that is all about Nike for mentions of the word "Adidas" to see what people think about their competitor. They may also just want to exclude the word "Nike" to get rid of that data and see what else is mentioned.

I am having a few issues here, but he is some things I'd love feedback and help on:

1) How to make it apparent what is being excluded vs included?

-I could make the "buckets" here Included and Excluded and just place all applied filters under each, instead of making the buckets the search type (ie: Author, Hashtag, Text, etc). Or there could be a combination of both? I am not sure which is more important to users at this moment.

2) Does one search make sense? Should I have a search for both include and exclude? or a search for each search type?

3) Does having the is/is not dropdown next to the search box make sense? Should it instead be next to each item?

So many questions! I would love some feedback on what makes sense and what doesn't in general to all of you as I ideate.

Current solution: Past Ideation: Thank you!

Answer 1

1) You could make it more apparent to which category each individual rule corresponds. E.g. coloring them green/red or replacing the IS/IS NOT with the mathematical symbols for equals/equals not or adding plus/minus signs somewhere there. I personally like that they are grouped under their search type buckets. It makes more sense because then you can see what values would be allowed for your Post Text, for example.

2) One search seems fine. I find it a bit weird that the search field starts with "Is not". Usually you specify which search type you want your query to work on (e.g. "Post Text") and then the operator and then the values (e.g. <2134>). I see that you want to include a convenience/efficiency function for the users there, so you guess the search type from the input which is also a nice idea.

3) It depends on the queries the users make. If they are long and complex (which is not the case in your example), it may be nice to give them the option to correct their input without having to type everything again. But then there should also be an option to edit the "values" field. But that also makes the UI more cluttered.