Entry information standard
BIII.eu software entry information standard
The standard described here (still under discussion) provides guidelines to support BIII.eu webtool curators to monitor the webtool content and tagging. This standard was adapted from the Tool information standard documentation from ELIXIR bio.tools. Thanks to Jon Ison for referencing this documentation.
This standard comprises a list of entry attributes to be specified for a software entry to be classified in a 5 tier rating of entry completeness and quality in BIII.eu.
In addition we provide curation guidelines describing how each attribute should be specified to ensure the quality of BIII.eu entries. These guidelines are not limited to the syntatic and semantic constraints defined by EDAM-bioimaging ontology and BISE-core-ontology
The standard provides a basis for monitoring of content and labelling of BIII.eu entries initially by:
- Entry completeness (3 tiers being "SPARSE", "DETAILED", and "COMPREHENSIVE")
The standard is applied to BIII.eu as follows (condensed information available from the tables):
"SPARSE": Minimum information requirement for new entries. A SPARSE entry may be invisible in the webtool (and made it clear to the curator adding the entry in the UI) by default and will only show after aditional information is added (similar to what occurs in bio.tools). A sparse entry has a Name, Description, Unique ID (automatically created) and type (collection, component, worflow, don't know). This category may not conform to biii.eu curation guidelines and for curation purposes, such entries must be shown in the list of 'to be curated' of confirmed taggers somehow as 'high priority.
"DETAILED": This is the mid-completeness category. An entry with 'Basic details' shall have implementation type (Library, plugin, standalone, and web application), Entry point (URL of the repository or 'official' website), an illustrative image (preferably a screenshot of the UI, or the input/output results, but logo whenever it fits), author ( in the form of
LastName, FirstName (ORCID ID)) and at least one function (EDAM-Bioimaging Operation Class, for example, model-based segmentation or object feature extraction). In this category there must be at least one attribute from the Accesibility and Use information groups. In addition, the programming language of the tool is defined as well as its execution platform (Operating System). This category may not conform to biii.eu curation guidelines and for curation purposes, such entries must be shown in the list of 'to be curated' of confirmed taggers without any warning.
"COMPREHENSIVE": Such entries would provide relevant information to users of all backgrounds and are useful resources and must include at least one attribute from the Documentation group, at least one Topic (EDAM-Bioimaging Topic Class, for example, fluorescence microscopy, Single molecule localization miroscopy and machine learning), one biological term (which is not a mandatory attribute, but highly recommended) and the DOI of its implementation. Since DOIs of implementations are still not common, this is also an optional attribute (See also: Making your code citable and DOI Registrations for software - DataCite Blog). The additional entry attributes that make an entry comprehensive are Additional keywords (not covered by biological terms or EDAM-Bioimaging) and at at least one training material attribute and may have more than just one biological term, EDAM-Bioimaging Operations and Topics. This category conforms to biii.eu curation guidelines and for curation purposes, such entries must be shown in the list of 'to be curated' of confirmed taggers without any warning.