-
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
Are the linkouts getting a bit GCV-redundant? #612
Comments
I agree that this probably should be simplified, but as an explanation of the differences we have:
I should add that we are also releasing pangene-level GCVs, which would be only genus-level but would potentially add yet another GCV choice to linkouts. So it's definitely a good time to decide how to make this all more "typical user"-friendly! |
The explanation isn't for me, it's for our users. I am aware that there are differences. But a random user has no idea how those links differ. |
Yes, I thought you might have suggestions on how to rephrase the link texts to make the distinctions clearer (without being overly verbose) |
Ahhhh, no, I'll leave that for you. :) I think we should just link one Mother of All GCVs. |
I guess that would be analogous to what we currently to for mine linkouts, ie only take people to LegumeMine, the Mother of all Mines. But you're tempting me to add links to the genus mines too so that the GCV weight is at least counterbalanced... |
I was looking at gene linkouts and realized that I don't know what the difference is between the three GCV linkouts. I understand that they're probably different, a difference which is understood by a few people on Earth, but do we want to make users figure out which one to click, or, rather, choose one that makes the most sense for the "typical user" (that doesn't work for LIS)?
The text was updated successfully, but these errors were encountered: