-
Notifications
You must be signed in to change notification settings - Fork 133
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
A clearer definition of "resources" #1518
Comments
One of the things that resulted from this discussion is that the icon is a wrench and the code snippet uses the word {% tool "toolname" %}, which is not really applicable when it is a policy, standard, etc ... |
Action list:
|
@bedroesb I think I like the first one better (but I am notoriously not good at graphics). |
I also like the first one more than others |
I do not like them all :( The most logical to me is the second one while being the most unattractive. The first is a compass for me, used to find North on a paper map. |
Description
Refer to https://rdmkit.elixir-europe.org/tool_resource_update
Whilst it is understandable what a tool is, the term "resource" is considerably more vague and open to interpretations.
The possibility of linking with FAIRsharing would make one think that "standards", "databases", and "policies" are all to be considered as "resources" and should be in the yml file. In the case of standards, this is implemented e.g. for MINSEQE
here. The same approach is, however, not implemented in many other pages (e.g. MIxS here).
Another interpretation of the FAIRsharing linking would be to use it for "standards", "databases" and "policies" which are supported by the various "tools" or "resources", in which case metadata standards should not be in the yml file. I am sure other interpretations are also possible.
Personally, I am in favour of the first interpretation, as it would provide richer information and the possibility of linking towards both the webpage of the "resource" and the registries (FAIRsharing, bio.tools, TeSS). One could also consider having other categories that behave as "tools" but use other icons (it would be weird to have that wrench icon close to e.g. a database or policy).
Independently from the paragraph above, we should clarify and be more explicit about what is a "resource" (i.e. what has to go in the yml file and what does not).
The text was updated successfully, but these errors were encountered: