from Bridget Wagner, Broad Institute. The "type 2 diabetes mellitus" results have no scores attached to them: https://ui.transltr.io/results?q=26394fad-bfd9-4e32-bb90-ef9d5044f593 I also don't know what "type 2 diabetes mellitus 2" and so on mean. Searching for diseases that don't have preset buttons (like "type 1 diabetes mellitus") returns an error.

[TranslatorIssueCreator]

Type: Other Comment

URL: https://ui.transltr.io/results?q=26394fad-bfd9-4e32-bb90-ef9d5044f593

ARS PK: a304b0df-e2de-4eac-8de6-fa06bb3734da

Steps to reproduce:

Screenshots:

[sierra-moxon]

the need for consistent node attributes is documented in a related issue: #92
the need for link outs to more information on subject/object nodes is documented in a related issue: #91

It is unclear why type 1 Diabetes Mellitus was not returning for the user? Just now, I was able to see the autocomplete performing as expected.

[sierra-moxon]

If I don't select a autocompleted term immediately, I do have issues with my session (the autocomplete stops working, even on reload of the page).

[dnsmith124]

I'm struggling to recreate the original bug here, but I think we can likely chalk this up to the NN or NR going down at the time the original user was attempting to perform a query.

Regarding the issue you were running into @sierra-moxon, I'm unable to recreate that issue as well. Clicking away from the query bar does cause the list of terms to go away so that the user can access the example diseases, but typing in the bar again will resubmit the search and return the terms again (even just adding a space). If the user doesn't click anything, the terms should remain visible indefinitely.

Is this behavior acceptable, or do we need to make an adjustment?

[sierra-moxon]

can close! :)