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

When uniprot records exist as old and new record- should identify this #5

Open
knaegle opened this issue Sep 30, 2022 · 2 comments
Open

Comments

@knaegle
Copy link
Contributor

knaegle commented Sep 30, 2022

Found that the API is returning the first record, even if multiple exist, for an accession. Should add a search that looks for all matches and gives the accessions that might be used to ensure update. (Ultimately, old uniprot records that are stored should be updated to add a notice that the uniprot ID is old).

@knaegle
Copy link
Contributor Author

knaegle commented Sep 30, 2022

A note that the current behavior is actually at the time of data formation and only one record, the one with more PTMs is returned.

@knaegle
Copy link
Contributor Author

knaegle commented Jul 24, 2023

This will be fixed in proteomescout v2.0 when the database migration has occurred and the flat file will never export an old protein record (and only export current protein records).

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

No branches or pull requests

1 participant