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
We have a new use case where we 'human protein' has 20,000+ children from Uniprot's reference proteome. Gizmos can generate HTML for 20,000 children, but most browsers will hang when they try to render it. So if a node has more than X (maybe 100?) children, we need another way to view them.
I've been thinking of searching the children with the table in #96, but I'm still a big fuzzy about exactly what we should show the user. Suggestions?
The text was updated successfully, but these errors were encountered:
We could just have a link under the parent class that says "browse N children" (or something like that) and directs you to the table. Then when you click on a term, it only shows that term under the parent and then the same "browse N children" link under that.
We have a new use case where we 'human protein' has 20,000+ children from Uniprot's reference proteome. Gizmos can generate HTML for 20,000 children, but most browsers will hang when they try to render it. So if a node has more than X (maybe 100?) children, we need another way to view them.
I've been thinking of searching the children with the table in #96, but I'm still a big fuzzy about exactly what we should show the user. Suggestions?
The text was updated successfully, but these errors were encountered: