We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What's your use case?
Datasets always outputs an instance of Table, even for data that would be more suited to Corpus.
What's your proposed solution?
Datasets could (should?) output Corpus when the data is more appropriate for text mining and Timeseries when appropriate for ts. A flag somewhere?
Are there any alternative solutions? Currently, the user has to explicitly use Corpus and set text features manually.
The text was updated successfully, but these errors were encountered:
Corpus migrates text_features to data attributes, which would, presumably, solve the problem (text_features is retained when loading the data).
text_features
Sorry, something went wrong.
No branches or pull requests
What's your use case?
Datasets always outputs an instance of Table, even for data that would be more suited to Corpus.
What's your proposed solution?
Datasets could (should?) output Corpus when the data is more appropriate for text mining and Timeseries when appropriate for ts. A flag somewhere?
Are there any alternative solutions?
Currently, the user has to explicitly use Corpus and set text features manually.
The text was updated successfully, but these errors were encountered: