Hi,
As best I can tell, workspace clones don't appear to inherit permissions (in my case, read permissions) from the original parent workspace. Is this correct? If so, is this intentional? It seems that the lack of inherited read permissions in workspace clones can present a roadblock for analyses.
For example: I'm in the process of analyzing a dataset of ~7.6k human Illumina 30X whole-genomes, and have been working out of a clone of the parent workspace where the data were originally stored. I have read/write permissions to the workspace clone, but initially wasn't given read access to the original parent workspace due to an oversight. Thus, although the subjects/samples/sample sets are identical to the original parent workspace, and my method configurations recognize the bam path attribute in the sample metadata, I can't actually access any of the files due to a permissions error.
I've attached a screenshot showing an example of such an error message.
Unless I'm misunderstanding, workspace clones don't provide read access to the data in the parent workspace unless the user already has read permissions in the parent workspace. Is this something potentially worth considering altering? It seems that inheriting read access to all data upon cloning a workspace might be a useful feature, because otherwise it doesn't seem that workspace clones serve much of a purpose absent access to the parent's data.
Thanks,
Ryan Collins
PhD Candidate, Talkowski Lab
MGH / Broad / HMS
rlcollins@g.harvard.edu