Skip to content
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

Feature request: option to deploy human-readable format in parallel with binary deployment for datasets #788

Open
ntentes opened this issue Sep 22, 2023 · 1 comment
Labels
feature a feature request or enhancement

Comments

@ntentes
Copy link
Member

ntentes commented Sep 22, 2023

A common workflow for me is to deploy a pin containing a dataset to Connect in both a binary and human-readable format. This usually happens when R/python users want a fast, consistently typed binary (like qs or arrow) and other business users want to be able to download from Connect in csv format to pull into a spreadsheet.

Currently, I have to deploy both of these separately with unique names (and GUIDs). When distributing the pin or a when a user searches for the pin in Connect, I either have to inform them of both deployments/names or give them the correct link/name based on their tooling.

For example, my pin_write() calls usually look like this:

board %>%
  pin_write(account_information, 
            name = "account_information", 
            type = "arrow"
            )

board %>%
  pin_write(account_information,
            name = "account_information_csv", 
            type = "csv"
            )

I'm not sure of the best way to implement this in terms of interface, but in my mind's eye I see something like an option to include_human_readable:

board %>%
  pin_write(account_information, 
            name = "account_information", 
            type = "arrow",
            include_human_readable = TRUE
            )

or even an option to include multiple types:

board %>%
  pin_write(account_information, 
            name = "account_information", 
            type = c("arrow", "csv")
            )

Another benefit of "coupling" multiple deployment types of the same deployment could be having import redundancy in the case that the pin reader does not have the required package to download a special type like arrow or qs.

Thanks!

@juliasilge
Copy link
Member

juliasilge commented Sep 25, 2023

I like this idea a lot!

board |>
  pin_write(account_information, 
            name = "account_information", 
            type = c("arrow", "csv"))

We do already have the ability to store multiple files together in a pin in pin_upload() so this might not be too tough.

@juliasilge juliasilge added the feature a feature request or enhancement label Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature a feature request or enhancement
Projects
None yet
Development

No branches or pull requests

2 participants