Skip to content
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

Open
bianchini88 opened this issue Aug 7, 2024 · 8 comments · May be fixed by #1532
Open

A clearer definition of "resources" #1518

bianchini88 opened this issue Aug 7, 2024 · 8 comments · May be fixed by #1532
Labels
idea-for-discussion This can be used for inviting discussion from collaborators or community in general

Comments

@bianchini88
Copy link
Collaborator

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).

@bedroesb
Copy link
Member

bedroesb commented Aug 30, 2024

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 ...

@bedroesb bedroesb added the idea-for-discussion This can be used for inviting discussion from collaborators or community in general label Aug 30, 2024
@bedroesb
Copy link
Member

Action list:

  • Define resources in the "Add new tool and resources list"
  • Go through the pages to identify standards/policies and databases that doe not yet make use of a snippet
  • Check if the relevant resources have the correct FAIRsharing ID
  • Decide on a new icon when it is not a tool
  • Discuss if we want a new snippet for resource instead of only "tool"

@bedroesb
Copy link
Member

What do we think of this icon? @elixir-europe/rdmkit-editors
image

@bedroesb
Copy link
Member

I liked this one less:
image

@bedroesb
Copy link
Member

or this one:
image

@bianchini88
Copy link
Collaborator Author

@bedroesb I think I like the first one better (but I am notoriously not good at graphics).

@diana-pilvar
Copy link
Collaborator

I also like the first one more than others

@marikapop
Copy link
Collaborator

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.

@bedroesb bedroesb linked a pull request Sep 26, 2024 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
idea-for-discussion This can be used for inviting discussion from collaborators or community in general
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants