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

Strict checking of vocabulary-controlled fields #148

Closed
lwaldron opened this issue Sep 23, 2022 · 16 comments
Closed

Strict checking of vocabulary-controlled fields #148

lwaldron opened this issue Sep 23, 2022 · 16 comments
Assignees
Labels
priority necessary for early utility

Comments

@lwaldron
Copy link
Member

Body site, Sequencing platform, and Statistical test currently allow free-form entry even though we have lists of allowed values. Here is an example: https://bugsigdb.org/Study_563/Experiment_2

Can we lock these down to only allow use of the allowed vocabulary? I saw a curator who had entered mixed-capitalization of the Condition field this summer but had already corrected it, and I wasn't able to free-form Condition, so I guess this has since been locked down?

@tosfos
Copy link
Collaborator

tosfos commented Sep 29, 2022

Will do

@tosfos
Copy link
Collaborator

tosfos commented Oct 4, 2022

We restricted these fields:

  1. Body site
  2. Condition
  3. Sequencing platform
  4. Statistical test

Please review and close if it looks good.

@ftzohra22
Copy link
Collaborator

ftzohra22 commented Oct 20, 2022

@lwaldron @tosfos It seems like the condition field is sometimes not auto-filling data from the ontology site/condition page (please check screenshot below from Study 181 that I'm curating). "Irritable bowel syndrome" is a valid EFO term as well as listed on our condition page but shows no results found. Given that this field is restricted, I'm also unable to enter it as free text. We've run into this issue once before with 'Huntington disease' but it was fixed the next day so I didn't bring it up.
image

@lwaldron
Copy link
Member Author

I confirm I also see the same as @ftzohra22

@tosfos
Copy link
Collaborator

tosfos commented Oct 20, 2022

We've been struggling with this type of issue for a while. Ultimately it looks like a PageForms bug. And indeed there's a note in the code internals that mentions that the feature will struggle with a large set of autocomplete values. We're going to spend some time on a full solution.

@lgeistlinger
Copy link
Collaborator

Just noting that I experience the same for the body site field when eg trying to enter an existing term "buccal mucosa":
Screen Shot 2022-10-22 at 10 54 49 AM

@lwaldron
Copy link
Member Author

I hear this is interfering with curation, so is there some temporary workaround if the proper solution will take a while?

@tosfos
Copy link
Collaborator

tosfos commented Nov 14, 2022

We'll check. I also bumped up the priority for this task.

@lgeistlinger
Copy link
Collaborator

Hi @tosfos just wondering what is the status of this one?

@lgeistlinger lgeistlinger added the priority necessary for early utility label Dec 13, 2022
@lgeistlinger
Copy link
Collaborator

This would be a priority for us as it precedes other clean-up of eg body sites in #151

@lwaldron
Copy link
Member Author

Agreed, this should be top priority because it is still interfering with curation.

@tosfos
Copy link
Collaborator

tosfos commented Dec 13, 2022

We've been waiting for the script that's resolving #111 to complete. That script does look done now, so we'll move forward on this. We'll have to perform a container restart. If all goes well, this should be resolved by tomorrow.

@tosfos
Copy link
Collaborator

tosfos commented Dec 14, 2022

We believe things should be much improved. Please test and let us know what you find.

@lgeistlinger
Copy link
Collaborator

Can confirm - tested the terms that gave issues above and autocomplete would show up fast with these terms. Can we remove the note "Due to a temporary issue, autocomplete may not load the full list of possible options." from the entry form @tosfos? This can then be closed.

@ftzohra22
Copy link
Collaborator

Checked and can confirm its working
image

@tosfos
Copy link
Collaborator

tosfos commented Dec 14, 2022

That's great news! Removed the warning on both Experiments and Signatures.

@tosfos tosfos closed this as completed Dec 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority necessary for early utility
Projects
None yet
Development

No branches or pull requests

4 participants