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
theathorn opened this issue
May 25, 2021
· 4 comments
Labels
--[priority] Lowcode[subject] Production codeenh[type] New feature or requestepic[type] Issue consists of multiple smaller issuesorange[process] Done by the Azul teamspike:2[process] Spike estimate of two points
The label values for e.g. library_preparation_protocol.library_construction_method (see HumanCellAtlas/dcp2#13) contain slight variations in the text used, which are then visible in the Data Browser. Indexing by looking up the ontology id would eliminate this issue.
The text was updated successfully, but these errors were encountered:
The birds-eye view is to download and parse the HCAO ontology and convert a mapping at build time. The index loads the mapping and translates every term ID found in the metadata to the corresponding label. If no label is found in the mapping, the indexer logs a warning and falls back to the label / text in the mapping. Our metadata API needs to be extended to expose .ontology, .text and .label instead of eagerly choosing one of them. None of this affects the Azul API or the browser. The only externally visible effect will be that the service response contains the latest labels instead of the stale ones from the metadata.
Converted this to an epic and added first child issue. Will add more child issues as the first child nears completion. There are some TBDs that I can only decide after we get more expertise with RDF, OWL and OBO.
--[priority] Lowcode[subject] Production codeenh[type] New feature or requestepic[type] Issue consists of multiple smaller issuesorange[process] Done by the Azul teamspike:2[process] Spike estimate of two points
The label values for e.g. library_preparation_protocol.library_construction_method (see HumanCellAtlas/dcp2#13) contain slight variations in the text used, which are then visible in the Data Browser. Indexing by looking up the ontology id would eliminate this issue.
The text was updated successfully, but these errors were encountered: