discrepant MDR accession ID in web app and api response

[delwen]

In some cases, when I query the API to get the MDR accession ID corresponding to a trial, I get an ID that is different to the one in the web app.

For example, I am interested in the EUCTR trial 2010-022235-10. I query the API to get the MDR accession number as follows:

https://crmdr.ecrin.org/api/Study/MDRId/100123/2010-022235-10

where 100123 is the integer for the trial registry source and 2010-022235-10 is the trial id (per your documentation and this mapping I found: https://github.com/ecrin-github/rms-portal-new/blob/504c09340f6af24f42c6d9996da9cbf8a458beeb/src/app/pages/common/study/upsert/upsert-study/upsert-study.component.ts#L428)

This returns the MDR accession ID 2545509. When I then query the API for study details corresponding to this MDR ID (https://newmdr.ecrin.org/api/Study/2545509), I get an empty API response. I looked into this and realised that when I search for 2010-022235-10 in the MDR web app and look at the study details, I see in the URL that this trial actually seems to correspond to the internal MDR accession ID 2430271.

I see this for a number of trials, e.g., 2012-003989-40 (MDR accession ID I got was 172800 but seems to be 2141319).

I'm also curious why in some cases the MDR accession ID is a 6-digit integer and other times a 7-digit integer.

[sergiocontrino]

probable link to failed update of search tables (see comment on #54)