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
Various organizations would benefit from sharing OCF sample data with one another. Are the GitHub repos a sufficient place for storing these? Would it be better to have a dropbox-like app on opencaptablecoalition.com where authenticated users can upload/download sample data?
For discussion -- created while working through the comments sheet attached to issue #507
The text was updated successfully, but these errors were encountered:
The opencaptablecoalition.com domain hosted by WSGR uses Google Cloud Storage currently on the backend to host the public schema files
We could possibly leverage the same technology to host munged/scrambled data sets publicly
** Ethan Garofolo said we would need to do some research do see what affordances this technology allows w.r.t. allowing users to upload directly
Summary: I don’t think trying to add authenticated file uploads to the main website is a sensible thing to pursue and recommend starting with a GitHub repository.
I looked into the technology used for building the main website (Webflow). We use it as a visual page builder, and the product seems best suited to brochureware.
At present, I think a GitHub repository would be the best approach for hosting data sets. We’d already have authentication and authorization, and if people need programmatic access, they could always use the raw content URL for a given file.
It might be worth more research to verify how members want to use the test files, but for starting at least, my recommendation is to go the GitHub repository route.
Various organizations would benefit from sharing OCF sample data with one another. Are the GitHub repos a sufficient place for storing these? Would it be better to have a dropbox-like app on opencaptablecoalition.com where authenticated users can upload/download sample data?
For discussion -- created while working through the comments sheet attached to issue #507
The text was updated successfully, but these errors were encountered: