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
{{ message }}
This repository was archived by the owner on Sep 12, 2019. It is now read-only.
It would be awesome if there existed User profiles, linked to ORCID, where researchers could own projects and say where they've used other tools in the toolbox (papers, presentations, blogposts, etc.)
In this way we'd get a network of researchers and the open scientific software they use, thereby improving the discoverability of certain niche tools.
The text was updated successfully, but these errors were encountered:
So the way I imagine this working is that you sign up for a ScienceToolbox account using GitHub or BitBucket, and your ORCID ID, i.e. connect those three accounts: DVCS, ORCID and ScienceToolbox.
Once your DVCS account is connected, you can own your tools on ScienceTools (either you're the author of or you're a member of an organization and have commit rights), which means that you can edit the description on its Tool page (yet unexisting).
Having an account also means that you can enter uses for any tool on the site. If you've used a tool listed on Science Toolbox, you can click "I used this" and uniquely identify where you've used it, either with a DOI or an URL. It's probably OK to limit uses to things that are available on the web in some form. Whenever a new use appears, it can be e-mailed directly to the author of the tool.
Having an account also means you can comment on tools, perhaps. Still deciding on that. Comments can also be email directly to their authors.
It would be awesome if there existed User profiles, linked to ORCID, where researchers could own projects and say where they've used other tools in the toolbox (papers, presentations, blogposts, etc.)
In this way we'd get a network of researchers and the open scientific software they use, thereby improving the discoverability of certain niche tools.
The text was updated successfully, but these errors were encountered: