Skip to content

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

@knaegle

Description

@knaegle

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions