default privacy setting should be public
donovan-h-parks opened this issue · comments
It would likely be best if the default privacy setting for creating marker lists or adding genomes was public. In general, we are looking to share our data across ACE and build synergy between different projects. Only in some rare cases would I expect a user to need/want to make their data private.
-1
What's the point if we can (and generally do) make trees out of all the private genomes anyway? Private means not ready for publication, not private to the actual person.
Guess we should clarify the concept of public/private. My concern is to do with genome_lists and marker_sets. If someone makes a sweet genome list (all cyanobacteria) or a new marker set (TM6-specific) it would be nice to know about these and be able to use them. I suspect if people have to throw the --set_public flag to make these public they will rarely do so. I think a --set_private would be better.
Does the concept of a private vs public genome still exists?