curie identifier case variants (and bogus IDs) resolve in misleading ways

[jmcmurry]

I came across this while trying to retrace my steps researching parkinsons genes... Since I could not remember where I was but could remember the NCBI gene ID (6622), I tried typing it in manually but couldn't remember the prefix casing.

Workflows and breadcrumbs is a whole other issue that is much more important but out of scope for this ticket. Though the bug is annoying, not the highest priority to fix due to infrequency with which direct typing is likely to happen. Capturing it anyway for posterity.

1) mixed case NCBIGene

This is as intended : http://monarchinitiative.org/gene/NCBIGene:6622

2) lowercase 'ncbigene'

Misleading as dead end: http://monarchinitiative.org/gene/NCBIgene:6622

• [ ] Should redirect

  3) bogus ID

Misleading as dead end: http://monarchinitiative.org/gene/FOOBAR:6622

• [ ] Should be 'sorry not found' in the way the resolver handles it:

[jmcmurry]

https://monarchinitiative.org/disease/orphanet:276413 does not resolve because it expects https://monarchinitiative.org/disease/Orphanet:276413 to be case sensitive

[jmcmurry]

@TomConlin I don't know if your recent work can be leveraged here?

[TomConlin]

... now expects to be ORPHA:

Think the alternative prefix map could have a lower case to whatever is prescribed then the interface fix its input to lower case to query the map.