Skip to content

Curator guidelines in BIII.eu - and its relation with EDAM-bioimaging Topic #12

@Leandroscholz

Description

@Leandroscholz

Dear @matuskalas and team,

While writing curator guidelines to BIII.eu, I stumbled upon a curious guideline from biotools and I wanted to know your opinion about it.

In biotools Docs, curator guidelines in Topic it says:

1. MUST specify the single most important and relevant scientific topic

AND

3. SHOULD NOT exhaustively specify all the topics of lower or secondary relevance

Well, the approach some taggers took in BIII.eu, including myself, was to add more than one Topic to the entry. For example if I knew a tool was developed and tested for a specific type of imaging modality, say, fluorescence microscopy, I would add it as a Topic. In addition, I would also add Machine Learning if I knew the tool used such a technique to solve the problem.

If we took the same guideline, we would rather choose Machine Learning (or fluorescence microscopy) the single most important relevant scientific topic. My whole point is: I would like to know the long term effect of adding two or more topics, even if the second (and following) might not be the most relevant.

I would assume that, by adding another Topic that is related to it it would make it easier for someone to find (may someone with a microscopy background would try to find tools that relate to a certain imaging technique rather than other type of topic). On the other hand, if taggers add too many Topics of secondary relevance, the search result could be cluttered with useless tools and would make it difficult.

So, what would be better? should we follow the same guideline as biotools or just recommend that at least one topic is added and not much more than that (2-3)?

Cheers,
See you soon in the next taggathon.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions