New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File passing error #6
Comments
@bhavikth is the value you are using for the "contains" and "does not contain" arguments? |
@clacinak I have tried entering all the possible values in the "contains" and "does not contain" field. Have tried both arguments as well as values which are not arguments. I’ve tried using the contains field searching for individual words and phrases within the description tag and even have tried using quotations and well as Boolean operators (Indiana AND University for example). I keep getting the same result where it passes for both the contains and does not contain field. It will still fail on either if the tag it is searching for is not present in the file. In short, the output which I get is the same for both "contains" and "does not contain" field. |
@clacinak Is it possible for you to have a video conference where I can demo you how we are using it. Because I feel, there might be some minute error in the way we are using it or if that's not the case, you will also be able to understand what the error is in a faster manner. |
When I select the filter "containing" or "not containing", I get the same output. The output should differ depending on the words/phrases it contains but it doesn't seem so. It is giving correct output for all the other filters but there seems to be some problem where files are being passed for both containing and not containing words and phrases within a given metadata field. Any idea on what the error might be?
The text was updated successfully, but these errors were encountered: