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
I had a discussion with some members of EJPRD who wanted to add some resources to bio.tools and they would like to have the possibility to store the tool logo somewhere in bio.tools so they can retrieve it and display it on their own website.
In regards to the biotoolsSchema we have a downloadType == "Icon" with the definition Icon of the software..
I am not sure if this refers to a favicon for a website or to an actual logo.
If it the intended use was for a logo then we should change the value of Icon to Logo, it makes more sense and there are no tools that are actually annotated with Icon download type. We can keep both in the beginning and phase out the Icon one.
If the intended use was for a favicon , like you see in the tabs of webpages, then we should rename it to Favicon and additionally add a Logo download type.
Thanks
The text was updated successfully, but these errors were encountered:
Indeed, it's a good idea to change the download type to "Logo", good now that nobody so far used the "Icon".
And for a favicon? I can imagine that it might be useful in the future to also be able to store a link to a small version of the logo, usable as an icon, in case of some big complicated logoi. Sounds again like a hierarchy of the types would be useful. But definitely not urgent anytime soon ;) (Future UX)
If needed, I can help with the XSD. (But not right these 2 weeks if anything bigger)
@joncison @hmenager @matuskalas @piotrgithub1 @redmitry
I had a discussion with some members of EJPRD who wanted to add some resources to bio.tools and they would like to have the possibility to store the tool logo somewhere in bio.tools so they can retrieve it and display it on their own website.
In regards to the biotoolsSchema we have a
downloadType == "Icon"
with the definitionIcon of the software.
.I am not sure if this refers to a favicon for a website or to an actual logo.
If it the intended use was for a logo then we should change the value of
Icon
toLogo
, it makes more sense and there are no tools that are actually annotated withIcon
download type. We can keep both in the beginning and phase out theIcon
one.If the intended use was for a favicon , like you see in the tabs of webpages, then we should rename it to
Favicon
and additionally add aLogo
download type.Thanks
The text was updated successfully, but these errors were encountered: