All Protein2GO web services require a userid parameter to be specified in order that proper authentication can be performed. Please contact goa@ebi.ac.uk for further details.
Inserts an annotation into the database. A certain amount of (predominantly syntactic) checking is done of the annotation data, and any annotation that fails this checking will be rejected.This checking encompasses most, but not all, of the checking that is usually performed by the Protein2GO client; it is, however, possible for an annotation to be created that is not semantically correct.
Note: All new annotations created using this service have their source set to PRIV, which means that they will not be published as part of the UniProt-GOA annotation set until a curator has loaded them into Protein2GO and upgraded their source to the appropriate value, and corrected any errors which were not caught by the syntactic checking.
*userid - see above
*AC - UniProt accession
*EVIDENCE - evidence code
*GOID - GO identifier
*QUALIFIER - qualifier
*REF_DBC - reference database code (PMID, DOI or GO_REF)
*REF_ID - reference identifier
*WITH_STR - with string
*ANN_EXT - annotation extension
*EXTRA_TAXID - interacting taxon id
http://www.ebi.ac.uk/internal-tools/protein2go/InsertAnnotation?userid=myuserid&AC=B0GUS5&EVIDENCE=ND&GOID=GO%3A0003674&QUALIFIER&REF_DBC=GO_REF&REF_ID=0000015&WITH_STR&ANN_EXT&EXTRA_TAXID |
Associates a comment with an annotation.
*userid - see above
*ann_id - identifier of the annotation to which the comment is to be attached; the annotation must exist, and be from an internal source (i.e., one with a stable identifier)
*topic - the topic of the comment - note that this must be one of the topics defined in the CV_ANNOTATION_COMMENT_TOPICS table, and which is not reserved for system use.
*text - the contents of the comment
http://www.ebi.ac.uk/internal-tools/protein2go/InsertAnnotationComment?userid=myuserid&ann_id=2153264&topic=General&text=Arbitrary%20text%20string |