To me, Dataverse and Figshare are NOT "Storage add-ons" or "Storage" integrations - integration/add-on, YES, but not “storage”, they are archiving repositories. Maybe “archiving” isn’t a good word, but definitely not “storage”. Though I see why they are being (lumped together) and called “storage locations” since that’s the text “Storage providers” at the top of the list of files.
One thing I want to stress is that Dataverse (and Figshare) are not the same as the other storage options (Box, Amazon S3, Dropbox, Github, etc.). Dataverse and Figshare are repositories used for the “final” versions of research. Files made public in FigShare and Dataverse should be the final versions of files.
I participated in the webinar for Internet Archive / OSF and as I listened to the workflow of “bagging” OSF registrations and then sending to IA…., I was thinking that process could also be done for Dataverse, either prepare “bags” for ingest (manually) to dataverse, or have OSF push the bag of a registration or a public project to a Dataverse dataset. Lots of possibility there!
I would love to talk about the possibilities, especially to talk about how to get Dataverse/OSF better integrated.
--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/d765d1ca-6e1f-45e1-9cf8-d4fa835bc43an%40googlegroups.com.