-
Notifications
You must be signed in to change notification settings - Fork 204
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
Minor tweaks to last two columns in ontology table on home page #2611
Comments
@nlharris It might be less of an issue with the pending work over on the dashboard to slim down to badge width, but the original intent here was to avoid packing in too many columns (it causes the description column to bunch up quite a bit). Agree that the current configuration is imperfect, though. |
I personally dont agree with suggestions two (add column makes the table too wide) and three (removing the social column should be done independently of this question here). What about renaming the "Re-use" to "Interoperability" or "OBO Principles"? Both the Dashboard checks and the license pertain to that.. |
Add one, remove one, relabel one! But, ok, fair point that removing the social column should be a separate decision.
|
The second-to-last column of the ontology table is currently labeled "Re-Use", but it contains both the dashboard results and the license. I was in favor of separating those into separate columns, but there was concern that that would make the table too wide. The proposed compromise was to change the column header, as I have done. address #2611
The second-to-last column of the ontology table is currently labeled "Re-Use", but it contains both the dashboard results and the license. I was in favor of separating those into separate columns, but there was concern that that would make the table too wide. The proposed compromise was to change the column header, as I have done. address #2611
The new home page ontology table looks amazing! 🙌
I have some suggestions for the last two columns (discussed in Slack with @nataled):
@jsstevenson
The text was updated successfully, but these errors were encountered: