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
Our current implementation relies on attribute checks (hasattr for ontology_id, _ontology_id_field, _name_field) to differentiate ontology registries from other BioRecord registries. This approach lacks robustness as unique identifier fields vary across registry types (some ontologies use ontology_id while Genes use ensembl_gene_id or stable_id depending on organism). We need a more explicit architecture to properly distinguish between registry types and their unique constraints.
The text was updated successfully, but these errors were encountered:
Our current implementation relies on attribute checks (
hasattr
forontology_id
,_ontology_id_field
,_name_field
) to differentiate ontology registries from other BioRecord registries. This approach lacks robustness as unique identifier fields vary across registry types (some ontologies useontology_id
while Genes useensembl_gene_id
orstable_id
depending on organism). We need a more explicit architecture to properly distinguish between registry types and their unique constraints.The text was updated successfully, but these errors were encountered: