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
Drugs are often given company- or target-specific code names, with a prefix followed by an ID number (for example, AstraZeneca uses the prefix AZD for in-development therapeutics -- their COVID vaccine was originally named AZD1222). However, curators inconsistently format these codenames, sometimes using a space (AZD 1222), sometimes a dash (AZD-1222), and sometimes no separator (AZD1222), and our sources may not include each possible form as aliases. We should assemble a list of such prefixes and ID structures and enable a check for matches under each possible form if a user's query looks like it conforms to this structure. This behavior could look similar to the current namespace inferrence that we can perform for some kinds of concept IDs.
The text was updated successfully, but these errors were encountered:
Drugs are often given company- or target-specific code names, with a prefix followed by an ID number (for example, AstraZeneca uses the prefix AZD for in-development therapeutics -- their COVID vaccine was originally named
AZD1222
). However, curators inconsistently format these codenames, sometimes using a space (AZD 1222
), sometimes a dash (AZD-1222
), and sometimes no separator (AZD1222
), and our sources may not include each possible form as aliases. We should assemble a list of such prefixes and ID structures and enable a check for matches under each possible form if a user's query looks like it conforms to this structure. This behavior could look similar to the current namespace inferrence that we can perform for some kinds of concept IDs.The text was updated successfully, but these errors were encountered: