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

Add a subject area tag/classification to the already present software tag #677

Open
sylvaticus opened this issue Feb 11, 2020 · 2 comments

Comments

@sylvaticus
Copy link

With the aim to improve the browsing of the many papers, I think the classifications of the papers should include a dimension relative to the application area of the paper, not just the programming language used.

Then one can choose an open classification (tags) or a predefined hierarchical classification (there are many)..

@arfon arfon transferred this issue from openjournals/openjournals.github.io Feb 11, 2020
@arfon
Copy link
Member

arfon commented Feb 11, 2020

This is already part of what our authors do, the tags include domain labels which are shown on the paper view page (e.g. https://joss.theoj.org/papers/10.21105/joss.01834) and https://joss.theoj.org/papers/tagged/exoplanets .

Then one can choose an open classification (tags) or a predefined hierarchical classification (there are many).

I've yet to find one sufficiently complete for JOSS but would love to be wrong. Could you suggest a few that you think might be sufficient?

@nichtich
Copy link

nichtich commented Jun 22, 2023

I'd recommend to use two knowledge organization systems:

1, a broad, generic classification for browsing (such as
2. a more specific controlled vocabulary for linking software with similar fields

For the second I recommend to use Wikidata. For the first there are several classifications and all are opiniated. Just stick to one of them. Candidates:

Why not use Wikidata only? Because the articles will get fragmented and there is no clean, stable hierarchy. In terms of information retrieval: better recall.

Why not use only a broad classification? Because every classification is too broad in specific areas. In terms of information retrieval: better precision.

This was referenced Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants