search

phac-nml / irida

Canada’s Integrated Rapid Infectious Disease Analysis Platform for Genomic Epidemiology
https://irida.ca
Apache License 2.0
40 stars 31 forks source link

Allow physical copying of samples #60

Open tom114 opened 6 years ago

tom114 commented 6 years ago

Matthew Walker suggested he would like the ability to be able to physically copy samples in the system rather than just linking. The concern is that samples may be linked from project x to project y, and a manager on project y may make changes to the sample (such as deleting files) without knowing it will affect project x.

Imported from GitLab issue #344. Originally posted on 2015/12/15 01:34PM

apetkau commented 6 years ago

This is also relevant for issue #211 where assemblies are associated with SequenceFile (specifically SequencingObject). Right now, since samples are linked, modifying an assembly for a sample (if that was ever implemented) would lead to the same issue.

Imported from GitLab. Originally posted on 2016/09/27 03:33PM

tom114 commented 6 years ago

Probably. The main problem to consider though is that we assume a SequenceFile comes from a single Sample. Copying a Sample will probably mean copying all associated SequenceFiles (database objects) as well.

Imported from GitLab. Originally posted on 2015/12/15 02:51PM

tom114 commented 6 years ago

This is a fine idea to me.

Should we use a terminology change in the UI to explain the difference to the user between copying and linking? "Copy sample to project" and "Link sample to project"?

Imported from GitLab. Originally posted on 2015/12/15 02:27PM Originally posted by Franklin Bristow