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
I can get all of the variables which is nice. Some variables, which I will list, have no constraint enums. This hinders some useful parsing in goat-cli. Full list:
bioproject
biosample
busco_lineage
in_progress
insdc_open
insdc_submitted
published
sample_acquired
sample_collected
sample_collected_by
sample_sex
sex_determination
To be explicit, biosample (rendered in md) has a length of 32 on constraint, but no actual fields:
"But part of the problem here is that it doesn't make sense to use an enum to restrict the input values for fields like bioproject and biosample as the potential list is so long. I think a better solution may be to apply a regex constraint on these fields, or to export the list of unique values from the index (this can be cached so only needs to generated once per release) either as part of this endpoint or something similar to the sources report that includes counts per value."
The text was updated successfully, but these errors were encountered:
In pulling the public JSON:
I can get all of the variables which is nice. Some variables, which I will list, have no constraint enums. This hinders some useful parsing in
goat-cli
. Full list:To be explicit, biosample (rendered in md) has a length of 32 on constraint, but no actual fields:
whereas family_representative does:
As you mentioned @rjchallis:
"But part of the problem here is that it doesn't make sense to use an enum to restrict the input values for fields like bioproject and biosample as the potential list is so long. I think a better solution may be to apply a regex constraint on these fields, or to export the list of unique values from the index (this can be cached so only needs to generated once per release) either as part of this endpoint or something similar to the sources report that includes counts per value."
The text was updated successfully, but these errors were encountered: