Metabolite ID conversion gives different results, based on auto-select yes/no

Hi @nunogit ;

I'm testing goliath with the list of HMDb IDs that Freddie was working on:
HMDB00112
HMDB00295
HMDB00901
HMDB00935
HMDB01275
HMDB01877
HMDB13037

When I do autoselect, I get these results:

When I say I want to convert from HMDb to CHEBI, the results change (I have no mappings left):

And, when I change the IDs of HMDb from old to new ID structure, I get the following results:

(every ID but the last is similar... this could be due to mapping issues).

And with HMDB selected as primary database to map from (some mappings, but most do not work):

And last but not least, the ID that keeps giving "undefined" as a result, does exist in HMDB:
http://www.hmdb.ca/metabolites/HMDB0000901 . I can check if it is also part of our mapping files (could be that the webservice is still running on quite old data right?)...

Reproduce the conversion using the listed HMDB IDs, comparing autoselect, explicit HMDB-to-CHEBI conversion, old-to-new IDs, and HMDB as the primary database. Check the mapping files and webservice data mentioned in the report; done means the same valid mappings are returned consistently and HMDB0000901 no longer produces undefined.

Written by the indexing model from the issue text.