-
Notifications
You must be signed in to change notification settings - Fork 1
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
Create new analysis subtypes #55
Comments
term for transcriptome assembly (previously analysis_unigene): operation:3258 genome assembly: previously .... ? vanilla analysis : operation:0525 |
Problem with defining analysis unigene type: the module did not utilize the analysis_type prop. so we either a) have our unigene type depend on something else (ie analysis_unigene_name, which is what the module uses as the identifeir)….. buuuuut defining the type we say the prop is equal to something, not taht the prop exists or b) insert the prop into all of our analysis unigene analyses |
this update should work to make our existing unigene analyses have hte correct analysis type prop set |
This task is addressed by this "module" which we only want for the install script. https://github.com/bradfordcondon/tripal_manage_analyses Normally we would just re-migrate the analyses, but since we've put a lot of work into manually re-adding node fields, we don't want to do that here. This module will properly tag unigene analyses as transcriptomes or genomes based on their associated features, then migrate the entities from the plain analysis to the new type. It's not finished: something is wrong with my update query to the If this is something we would want to regularly do , then the module could be built up to be more general converting one entity type to another based on some criterion. |
Migrated for transcriptomes. GenomesOops, these were analyses not analysis unigenes.
|
Created and populated! |
Note: We still need types for blast and interproscan annotation |
Every analysis that requires custom fields needs a subtype.
tripal/tripal#224
The text was updated successfully, but these errors were encountered: