-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Port Haystack v1 DocumentClassifier node to Haystack v2 #7669
Comments
This is a legitimate request! I would start with implementing a The code should not be difficult to migrate, starting from the 1.x version. I will tag this issue as "contributions wanted" and see if any community members would like to address it. |
Good to hear... Yes, I think it should be placed in classifiers. |
This issue does't seem to have moved forward. I like to work on it. Thanks, |
Is your feature request related to a problem? Please describe.
I've been using the DocumentClassifier node in Haystack v1 with a zero-shot classification model to label documents with categories, which are attached to their metadata. We have recently migrated our code to Haystack v2 but have discovered that this component does not yet exist in v2, so I'm currently unable to classify documents.
Describe the solution you'd like
It would be great if someone were able to port this very useful v1 node into a v2 component please! It would also be tremendously useful to add the
multi_label
argument (see here) to the new component so that the model can be run assuming multiple labels can be true. The existing v1 node doesn't provide this flexibility, so I created a custom node by subclassing it and modifying it's behaviour.Describe alternatives you've considered
I considered creating my own custom DocumentClassifier component in v2, but have not started this yet, and am unsure about how difficult it would be.
The text was updated successfully, but these errors were encountered: