-
Notifications
You must be signed in to change notification settings - Fork 6
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
Things to amend - June 2023 #1323
Comments
@juanfmx2 I checked and regarding 2 it would be better if we had a text from elasticsearch without the time part ('T00:00:00'), because it will be fixed from the source, instead to having to apply the parsing everywhere it appears on the interface. |
Regarding task 1, now we can set up a custom configuration for certain properties. For example, for ChEMBL Release in documents, now you can select up to 100 bars, this means that you can see all the releases in the histogram: Screen.Recording.2023-07-04.at.15.54.34.movNow you can also sort by either key or count, this means that you can sort by the release name instead of the number of items of the bar: Screen.Recording.2023-07-04.at.15.57.40.movAs it was expected, the order is lexicographic. I tried to add a custom script to sort it in a 'natural' way, but it was not possible, and we will have the same problem when sorting on the table. I think is better to make a field with a name like 'release_label' that has the number first, and the values are something like:
That way we can sort it in a natural way easily. |
I think even if the number is leading it will not solve the sorting issue, because is will still be a string the only way to solve it is to add leading zeros to the the releases with a single digit (CHEMBL_01, CHEMBL_02, CHEMBL_03 . . . CHEMBL_09) |
Yes, you are right, my bad, the way to fix it would be to add leading zeros. |
It looks great now, thank you! |
The text was updated successfully, but these errors were encountered: