-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provided access to human split-out data. #296
Conversation
Previously no end-user access was provided to unconcented human split-out data. For each study a new iRODS group will be created. This pull request enables access to the nonconcented human data via this new group.
b521cdf
to
d99ebaa
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have a minor concern that moving some business logic from npg_irods to perl-irods-wrap will mean that maintenance becomes more complex (by coupling the two codebases more closely).
if (@groups == 1) { # Do not give access to nc human data to multiple groups. | ||
my $give_human_subset_access = 0; | ||
my @af_avus = $self->find_in_metadata($ALIGNMENT_FILTER); | ||
if (not @af_avus and $self->str =~ /_human[.]/xms) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you expand on why the path fallback check is needed? As this is in the base class the behaviour will be inherited broadly, including by legacy genotype code, which could be given incorrent permissions as a result.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I understand, there is an intention to create and store in iRODS split-out human data, which will or might originate from outside of the main NPG Illumina pipeline. This data might not belong to Illumina platform. The requirement for this task was to provide this scpecial level of access to files with names containing the _human
string. There is not firm agreement at the moment that fies like this will have the alignment_filter
metadata set. Therefore, the code covers both eventualities.
As far as I understand, the requirement is to inherit the behaviour broadly. Personally, I prefer the version of this implementation in #297 and a sibling wtsi-npg/npg_irods#439. It ishould also be possible, though I have not tried this, to move the expected_groups
method as it is in #297 to the npg_irods
package if it has a seq platform independent part.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll mark this as approved, but this change must not break https://github.com/wtsi-npg/genotyping which also depends on this package.
Previously no end-user access was provided to
unconcented human split-out data. For each study a new iRODS group will be created. This pull request enables access to the nonconcented human data via this new group.