Skip to content
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

Merged
merged 1 commit into from
Jan 18, 2024

Conversation

mgcam
Copy link
Member

@mgcam mgcam commented Dec 14, 2023

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.

@mgcam mgcam marked this pull request as draft December 14, 2023 12:45
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.
@mgcam mgcam force-pushed the read_permissions_for_nc_human branch from b521cdf to d99ebaa Compare December 14, 2023 14:31
@mgcam mgcam mentioned this pull request Dec 14, 2023
@mgcam mgcam marked this pull request as ready for review January 5, 2024 14:32
Copy link
Member

@kjsanger kjsanger left a 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) {
Copy link
Member

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.

Copy link
Member Author

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.

Copy link
Member

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.

@kjsanger kjsanger self-requested a review January 15, 2024 09:13
@mgcam mgcam merged commit d99ebaa into wtsi-npg:devel Jan 18, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants