How to connect identifiers in the mass spectroscopy and string database
2
0
Entering edit mode
9.4 years ago
Evergreeen • 0

Hi,

I have a problem with the identifiers in the mass spectrometry data and the STRING-db. I want to know how to connect these and use information in the project.Can you suggest if there are databases that can translate any of the identifiers in the ms data into ENSP?

Thanks

ENSP mass-spectroscopy STRING • 3.2k views
ADD COMMENT
0
Entering edit mode

Your question is very vague. The mass spec identifier depends on the software used to process the data. Which kind of identifer do you have?

ADD REPLY
0
Entering edit mode

Hi, We have MATLAB software...

ADD REPLY
1
Entering edit mode

I'm sorry, but it sounds like you have not made the effort of understanding what your "MATLAB software" is doing. MATLAB is a general programming language, and it is not descriptive of your problem.

ADD REPLY
0
Entering edit mode
9.4 years ago

String-db provides an index file to do mapping from major gene/protein databases (Ensembl, Entrez, Uniprot etc).

You can get the files here. You can use this for mapping.

protein.aliases.v9.1.txt.gz (445 Mb)    aliases for STRING proteins: locus names, accessions, descriptions...

Link to file: http://string.embl.de/newstring_download/protein.aliases.v9.1.txt.gz

ADD COMMENT
1
Entering edit mode

Friendly note: it's possible to filter by organism, reducing file size by a lot. (the homo sapiens alias file is only 13.7 Mb)

Edit: http://string-db.org/newstring_download/protein.aliases.v9.1/9606.protein.aliases.v9.1.txt.gz - per request.

ADD REPLY
0
Entering edit mode

Hi David, can you add species specific link here ? Thanks!

ADD REPLY
0
Entering edit mode
9.4 years ago
Evergreeen • 0

Hi,

It is MATLAB software and we need to connect mass spectroscopy identifiers to ENSP identifiers...

Thank you

ADD COMMENT

Login before adding your answer.

Traffic: 1440 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6