-
Notifications
You must be signed in to change notification settings - Fork 388
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
Export dataset to HF Hub from the UI #2520
Comments
So, ideally I was wondering if it would be possible to create a similar card where you add (title, description, buttonText and buttonLink), and potentially add
|
This issue is stale because it has been open for 90 days with no activity. |
Importing and exporting directly from the UI is a popular request in our community, so I'm removing this from stale. |
This issue is stale because it has been open for 90 days with no activity. |
This issue was closed because it has been inactive for 30 days since being marked as stale. |
This issue is stale because it has been open for 90 days with no activity. |
This issue was closed because it has been inactive for 30 days since being marked as stale. |
Is your feature request related to a problem? Please describe.
I want an action in the UI to push the dataset to the Hub. We currently can push two "types" of datasets to the Hub:
rg.load
At first, I would say the most relevant is type 2. as I think the main goal at firs is to let users keep a copy of the datasets (especially crucial for Argilla HF spaces) and be able to restore the dataset, as we do for most of our tutorials. But I'm open to additional export "types" which include the option to export type 2. as well.
Another thing to take into account, maybe for further iterations if this is a blocker is that users might want to push to a private dataset so we need to ask them for an HF token.
Describe the solution you'd like
I would like to have a button and modal box somewhere in the UI to push the dataset to the Hub. In this modal box we can require the users to input:
If something went wrong when pushing the dataset, provide a clear message to the user of what went wrong.
This will require to have the logic of pushing the dataset in the backend, and add
datasets
as a dependency for at least the server but I don't see an issue there.Describe alternatives you've considered
Using listeners or the Python client but this is already possible and leaves non-developers out of this feature.
Additional context
We have something along these lines in the
export-to-hub
(https://huggingface.co/spaces/argilla/argilla-streamlit-customs) but as I said first use case is pushing even without preparing for training.The text was updated successfully, but these errors were encountered: