You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, the current bundle is set where the analysisprop "local:interpro_results" = interpro_analysis.
This is actually in line with, say, blast, where the analysisprop format:1333 (blast results) = blast_analysis.
Assuming that old types set via analysis_property:Analysis Type = 'interpro_analysis' are migrated somewhere, we're OK. im not 100% positive they are though- i dont see it in the install.
I can see the reason for swapping this, since we want the bundle mapepd to a cvterm, not a flat "value" in the prop table. So we get rid of the generic "Analysis Type" prop type, since that prevents us from having multiple bundles using that term with different values. It does make sense, we just need to make sure we migrated tripal 2 analyses that used different terms properly.
Major bug: The default bundle storage cvterm is set wrong.
CVterm set by the node when creating interpro analysis:
The Cvterm used by the default bundle created by this module actually looks for the cvterm
interpro results
instead ofAnalysis Type
:The text was updated successfully, but these errors were encountered: