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
There is a GitHub issue regarding the want for DropBox support and it shows that the issue was resolved but I am not confident that the issue was fully corrected since it states in the issue that there isn't much demand for it.
Add to Figshare:
This seems like the better option but I am not sure about the process so I have a few questions:
Is there a Way Lab figshare login or do I create my own?
Is it like GitHub where there is a Way Science organization and then the datasets within it?
Based on the answers to my questions, we can then proceed in one direction.
The text was updated successfully, but these errors were encountered:
Sounds good. Let's not use DVC for this then. We should keep in mind that our pipelines would love to have DVC support for either Dropbox or OneDrive.
Let's go with the Figshare option.
Is there a Way Lab figshare login or do I create my own?
Yes, please create your own account. Make sure to connect your ORCID.
Is it like GitHub where there is a Way Science organization and then the datasets within it?
No, not to my knowledge. I think it's good for you to double check me, however, in case things have changed since I last looked. (it's possible there is a thing called "collections", i am not sure)
The procedure is to create a personal account, create a new dataset, fill in the metadata information (feel free to open a new issue to document these items), and then publish (mint a DOI).
Part of the metadata procedure will be to name authors of the dataset. We should discuss authors prior to publishing the dataset.
do we know if there is anything binding the data to prevent it from being public.
I believe that we are all set to publish the data publicly. However, I will double check with Tim
@gwaybio For the CFReT data, do we know if there is anything binding the data to prevent it from being public.
If not, there are two options for where to put this data. Currently, before any removal of images, it is a little over 2GB with 990 images. We can:
Based on the answers to my questions, we can then proceed in one direction.
The text was updated successfully, but these errors were encountered: