Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SLCO1B1 Gene Names (Protein Espression/Protein Selection) #966

Open
msevestre opened this issue Oct 5, 2018 · 4 comments
Open

SLCO1B1 Gene Names (Protein Espression/Protein Selection) #966

msevestre opened this issue Oct 5, 2018 · 4 comments

Comments

@msevestre
Copy link
Member

see Open-Systems-Pharmacology/Forum#232

From @SCarter79

Theres an error on your "Transport Proteins", you have 3 different subtypes all labelled as SLCO1B1. The gene ID's are correct however. Can you please update the "Gene Name" field to reflect this?

@UlrichSi
Copy link
Member

UlrichSi commented Oct 8, 2018

Might this be related to #946 ?

@SCarter79
Copy link

I think so to a point, however the naming convention of transporters may differ more e.g. SLCO is a group of important solute carriers for drug movement, but the SLC (solute carrier) group includes everything from glucose to bile acid transporters.
But also there is some issues with the SLCO group of transporters in PK-Sim as it will put them as efflux transporters as standard (rather than influx).

@UlrichSi
Copy link
Member

UlrichSi commented Oct 8, 2018

@SCarter79 If we had the gene name or number added, it would at least be possible to differentiate what database origin was used in the model.

I also noticed in the past issues with the transport direction - I fully agree with you. Since this is different from the gene name issue, it might be helpful to open up a separate issue for it. Let's see what @msevestre thinks about it.

@SCarter79
Copy link

I think gene name would be more helpful as the protein name should in theory be easily obtained from it? whereas gene number is more cumbersome (to me at least), but already exists in the current record.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants