You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Hi @anakin87,
I would like to work on this. If I am not wrong this ZeroShotDocument classifier must be ported here in align with Haystack 2.0 nomenclature?
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: