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

Images should not be simultaneously embargoed and not embargoed. #67

Open
matentzn opened this issue Jul 28, 2020 · 1 comment
Open
Assignees

Comments

@matentzn
Copy link

We have one case of a dataset that contains both embargoed and non-embargoed images:

TrumanWood2018public contains two images that are also in TrumanWood2018. In P2, datasets that are embargoed are deleted in their entirety - which means those two images get deleted, when TrumanWood2018 gets deleted.

This pattern should be replaced by another approach - I suggest moving the non-embargoed neurons over to the public set rather than referencing them from both.

@dosumis
Copy link
Member

dosumis commented Aug 3, 2020

This is a more general issue for data coming from CATMAID where the same neuron often gets referenced in multiple datasets. @Robbie1977 not sure of best solution here apart from adding dataset links to embargoed datasets only after setting to production.

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

No branches or pull requests

2 participants