-
Notifications
You must be signed in to change notification settings - Fork 2
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
52 control vocabulary for targeted structures #53
Conversation
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'm a little nervous calling the CCF terms a registry, given that we historically called it an "ontology" and now some are pushing for "parcellation terminology".
Suspect we might have to change this later, but likely we will want to wholesale rename Registry to something else, so I guess we can proceed as-is.
Is your concern about having it in a list of registries? Or in having the field that references it be registry? Because the latter is vestigial from using |
Okay, @dyf and I hashed this out
Future issue will be to get rid of the concept of a Registry and adjust the schema to point to taxonomies more directly. Since we aren't using the |
Okay those changes are in place, either of you can merge this and maybe make a ticket to track the larger change if you didn't already? |
After discussion w/ Saskia we decided:
See To do this I also had to add a new feature to |
Adds a new Mouse CCF class, use by doing:
from aind_data_schema_models.mouse_ccf import CCFStructure
and then:
etc
Also available are: