Column mixed up for tissue specificity and tissue distribution output?

Community Feedback Bug reports
1

Hi
tissue_specificity should have 1, 0.5, 0 , -0.5, -1, NA and tissue_distribution 1,0.75, 0.5, 0.25,-1, NA values (based on the documentation Target Prioritisation | Open Targets Platform Documentation ).
However, in the OT download (not the UI) the data seems to be reversed, in that i only see
tissue_specificity 1,0.75, 0.5, 0.25,-1, NA values eg; 0.75 is unique for tissue distribution not specificity
tissue_distribution 1, 0.5, 0 , -0.5, -1, NA values
Is there an error in these columns - or was this issue fixed in the new release (we are currently using v25.12)

2

Hi,

We recently updated our baseline expression data together with the accompanying specificity and distribution scores. The platform documentation is valid for the most recent release only which is why you see a discrepancy with the data you’ve downloaded.

Unfortunately we do not publish older documentation online at present. But if you are keen to use the 25.12 release data rather than the latest release with the refreshed data, I’d be happy to try my best to help.

3

Hi Tobi
Thank you for your speedy reply. Unfortunately I am stuck with at present the older version in our data-warehouse, so it seems I have developed some in-house scoring/ranking rules based on the newer release, which is not ideal. Would you be able to check the documentation for v25.12 for those two data columns to check if a) it was an issue then eg: values of 0.75 we incorrectly in tissue_specificity and/or there was an issue with these two columns where the data had been mixed up b) not an issue then and this was reflected in the documentation at the time, in which case can you let me know what they were so I can amend my rationale for how we score/rank the targets internally.
However, if I understand you correctly, I think you are saying there was an issue which was resolved in the recent update? In that case I currently have 2,051 targets with scores pulled in from OT v25.12 that currently have the incorrect data?
Thank you
Louise

4

Hi Louise,

Sorry for the delayed reply, I meant to reply last week but GitHub was down and then it slipped my mind. The documentation for the columns you mentioned can be found on github here:

There was no issue with the previous data it was simply out of date so we deprecated in favour of data that we’re a bit happier with. The old data is still fine to use and you should not be concerned.

Kind regards,
Tobi