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

Feature to remove unused EFO terms from depo-curation #1488

Open
eks-ebi opened this issue Nov 14, 2024 · 0 comments
Open

Feature to remove unused EFO terms from depo-curation #1488

eks-ebi opened this issue Nov 14, 2024 · 0 comments
Labels
Priority: Low Type: Enhancement Additional functionality to create Type: Task Investigation work, no code needed at this time

Comments

@eks-ebi
Copy link

eks-ebi commented Nov 14, 2024

As a curator, I want to be able to remove an EFO term from the list of terms in depo-curation when that term is no longer supposed to be used for annotation (e.g. if the term has been made obsolete in the source ontology, or if curators have identified a more appropriate term for that trait). At the moment, we can delete terms from the list, but only if they have never been assigned to a study. This is because, even if a trait has been removed from the current version of a study, it still remains assigned as a property of a previous version of that study, in the version history - and this prevents the curator from deleting the term.

There are different ways that this could be resolved:
e.g. use a "soft" delete approach that removes the unused EFO from the list of available EFOs, without actually deleting it from the database

This will need more discussion before choosing an approach.

@eks-ebi eks-ebi added Type: Enhancement Additional functionality to create Type: Task Investigation work, no code needed at this time Priority: Low labels Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Low Type: Enhancement Additional functionality to create Type: Task Investigation work, no code needed at this time
Projects
None yet
Development

No branches or pull requests

1 participant