-
Notifications
You must be signed in to change notification settings - Fork 91
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
Multiple creation of expressions #3
Comments
This is definitely on the roadmap! |
On a similar note to this, having a "clear all" from the inbox would be nice for when you are testing things, add a corpus of 150 items or so, and then remove the intent... I don't know if removing the intent is supposed to put everything back into the inbox, but that is currently how it is functioning. Perhaps, give an option when removing an intent to clear the associated expressions as well? |
@vantreeseba, removing an intent is indeed supposed to put everything back in the inbox. Additionally, we plan to add batch processing features to help you manage your data. |
Awesome, that will make this a lovely system to use :) |
Quick update, you can now choose to delete all associated expressions when removing an intent. |
Just as a note on this, I've deleted all my expressions, but in the parsing time (the status) its giving me a number that cannot be correct, as I only have ~15 expressions listed under intents, but it has ~300 parsed expressions total. I don't know if this is effecting the parsing time because its much slower than it was when I first started testing wit. If the expressions are being removed from the associations, but not actually being deleted, you may be doing a lot of useless work by parsing expressions that are "orphaned". |
Is there an update on the timeline for identifying duplicate expressions? This will be a "must have" for me once I start collecting user input. |
Normally we don't create duplicate expressions anymore. The last "path" to get a duplicate is to edit an expression and set the text to an existing expression text. We'll soon "close" this last path. Is there a chance your duplicates were created some time ago? We should maybe run a migration that removes existing duplicates. |
I just identified two methods of creating duplicates in my instance, which is less than a week old:
I believe method 1 should be a higher priority to resolve, as that is where I am most prone to producing a duplicate. |
Fair enough :) Will fix asap! |
@aripatrick Thanks for your feedback, this should be fixed now! |
I'll close that, please let me know if any suspicious behavior occurs |
I have manually created an intent with a sentence.
When I send this exact sentence, it add it in the inbox for validation.
I think it shouldn't if the sentence is exactly the same because it will add spam in the inbox.
Another problem : if I validate it, it add the exact same answer in the intent, so I have the sentence twice.
The text was updated successfully, but these errors were encountered: