-
The field has been removed as a tool may be used by several communities, but it is still listed in required.
However the ids are still linked to a specific community (related to #25 and #32 )
-
As benchmarking API is approaching the beta state, sooner than later people from the different benchmarking communities are going to need an easy way to submit their data sets.
A natural place wher…
-
Is the four-level accessibility models part of this data model release?
Accessibility models says who has access to what datas in OpenEBench, and can be as follow:
- Private.
- Restricted.
- Com…
-
The current woy of setting references (primary keys) is completely open, with exception of community prefixes. This schema allows for communities to use their own ids, however the structure of the dat…
-
@matuskalas says (from RostLab meeting 2016):
_- Modeling of versions may need rethinking: if we have multiple versions for a single tool for instance, then it will be difficult to maintain the des…
-
What should a tool curator do so that the "compiler" and "automated" entries are mark as fulfilled?
The word "compiler" doesn't have any search hits at http://biotools.readthedocs.io/
Thanks,
-
Federico says ...
"I think there should be some sort of automatic “broken link” detection. In fact, when the registry will be open and available to everybody and the number of registered service wil…
-
Added two branches
MongoImplement0.3: Data model as implemented in the Database.
openEBenchApiDM: Data model as obtained from openEBench (Scientific) API. _extended json files correspond to ?extend…
-
Hello,
I got NullPointerException when annotate the endpoint:
```
@ApiResponse(content = @Content(
mediaType = MediaType.APPLICATION_JSON,
array = @ArraySchema(schema = @Schema(
…
-
As we are officially adopting CURIEs, and we are using identifiers.org as the authoritative source of those prefixes used in the CURIEs, we should clearly document it