accepting "open" tools only
types of tool
commercial tools are OK
but consultancy services are out of scope
etc.

This would be a new page under http://biotools.readthedocs.io/en/latest/

From bio-tools/biotoolsRegistry#90

"be careful how to explain what is the tools registry - what is considered to be a resource, what is the content etc. It can be confusing for the reviewers coming from the outside. Must explain clearly "what is a resource / what exactly is registered" ?"

Ensure correct / consistent use e.g. attribute descriptions, restrictions / facets etc. in

• current API docs (http://biotools.readthedocs.io/en/latest/api_reference.html)
• next-gen API docs (http://biotools.readthedocs.io/en/latest/api_reference_dev.html)
• JSON attributes description (http://biotools.readthedocs.io/en/latest/api_attribute_model_dev.html)
• Curators Guide (http://biotools.readthedocs.io/en/latest/curators_guide.html)

Jon and @ekry to work on this together : the first step being to align biotoolsSchema and JSON model internally, then fix docs above.

http://biotools.readthedocs.io/en/latest/curators_guide.html

Feedback needed please

e.g. http://biotools.readthedocs.io/en/latest/curators_guide.html#id7

which may be arising (but perhaps not :) ) because of non-unique headers.

cc @hansioan FHI

IDs user-editable at registration time (planned)
IDs then verified by bio.tools
Once verified become stable
Additional IDs can be created (in exceptional cases) for a tool, and all will resolve in perpetuity

prob.; just add a note that it's OK to have multiple primary publications, e.g. where the same thing is published in NAR year after year.

Explicit statement that the data in the registry is open, for other developers, and always will be (to encourage contributions)

in readthedocs, but also on the main site

http://biotools.readthedocs.io

Update tool - Permissions offers options:
Make this resource editable by me only
Make this resource editable by anyone
Make this resource editable for a specifed list of users

Could we create our own 'specifed list of users' (also maybe change this to 'specified list of users') or only predefined persons (not sure how) are allowed? E.g. I would like to add my collaborators to be able to update descriptions of our tools, however i can only add direct ELIXIR employees.

i.e. start annotating in bio.tools and copy the JSON for later reuse

Even some basic instructions would help the user

cc @hansioan

Provide this for common tasks as part of improved docs (suggestion from user)

see advice in bio-tools/biotoolsRegistry#473

in Curators Guide

Is it possible to define custom label, as it seems that some labels defined within 'Browse resources by popular terms' (https://bio.tools/) do not exist anymore in the drop-down menu and some useful are missing?

Crosslink from http://biotools.readthedocs.io/en/latest/api_attribute_model_dev.html to http://biotools.readthedocs.io/en/latest/curators_guide.html

We've had several requests how to use wget to get all results in one call, or rather, how to use pagination.

A new section in http://biotools.readthedocs.io/en/latest/api_reference.html including an example script would save us time in the long run.

It's a bit unclear currently, see edamontology/edam-bioimaging#12 (comment)

see https://github.com/bio-tools/biotoolsSchema/milestone/4

Heinz says ... "Documentation might also include hints on how to use the web interface. Currently, it mainly describes the API"

By default, search results are sorted on 'Score'. I couldn't find an explanation of this scoring system in the documentation.

I just hit the api to do a count of programming languages used in bioinformatics tools. Hit one 'Julia' entry which is currently not an allowed value (should be added to allowed values). Also found 107 'JavaScript' entries and 298 'Javascript' entries (lowercase 's'). Only 'JavaScript' is an allowed value. All 'Javascript' entries should be updated to 'JavaScript'. Thanks!

i.e. these sorts of links:

https://bio.tools?credit=sib

currently the docs (http://biotools.readthedocs.io/en/latest/api_reference.html) does not describe this

Currently, bio.tools domains cannot be accessed through the dedicated URLs as described in biotools_domains.rst. Perhaps this happened while moving the server?