Property talk:P686

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

Gene Ontology ID
identifier in the Gene Ontology

Description	ID in the Gene Ontology
Applicable "stated in" value	Gene Ontology (Q135085)
Data type	External identifier
Domain	According to this template: molecular function, biological process, or cellular component (objects of molecular function (P680) cell component (P681) biological process (P682)) According to statements in the property: molecular function (Q14860489), biological process (Q2996394) or cellular component (Q5058355) When possible, data should only be stored as statements
Allowed values	GO:\d{7}
Example	metal ion binding (Q13667380) → GO:0046872 vacuole (Q127702) → GO:0005773
Source	http://amigo.geneontology.org/
Formatter URL	http://amigo.geneontology.org/amigo/term/$1
Tracking: usage	Category:Pages using Wikidata property P686 (Q97769404)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P686 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 123,418 Main statement 44,150 35.8% of uses Qualifier 2 <0.1% of uses Reference 79,266 64.2% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Format “GO:\d{7}”: value must be formatted using this pattern (PCRE syntax). (Help)

List of violations of this constraint: Database reports/Constraint violations/P686#Format, hourly updated report, SPARQL

Single value: this property generally contains a single value. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P686#Single value, SPARQL

Distinct values: this property likely contains a value that is different from all other items. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P686#Unique value, SPARQL (every item), SPARQL (by value)

Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)

List of violations of this constraint: Database reports/Constraint violations/P686#Scope, hourly updated report, SPARQL

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P686#Entity types

Type “molecular function (Q14860489), biological process (Q2996394), cellular component (Q5058355)”: item must contain property “instance of (P31), subclass of (P279)” with classes “molecular function (Q14860489), biological process (Q2996394), cellular component (Q5058355)” or their subclasses (defined using subclass of (P279)). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: biological process (Q2996394), molecular function (Q14860489), cellular component (Q5058355)
List of violations of this constraint: Database reports/Constraint violations/P686#Type Q14860489, Q2996394, Q5058355, SPARQL

This property is being used by: ca:Plantilla:Infotaula d'enzim, ca:Plantilla:Infotaula enzim es:Plantilla:Ficha enzima Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

include "GO:" in identifier?

I tend to think that the identifier should include the prefix "GO:" because that's how they are commonly written out. (For example the accession for dendrite development is "GO:0016358", not "0016358".) This is in contrast to most other identifiers (UniProt, Ensembl, Refseq, etc.) where they do not add a leading prefix. The only other example I think is MGI (e.g., Mouse Reln has ID "MGI:103022", not "103022". Thoughts? Cheers, Andrew Su (talk) 16:45, 11 July 2013 (UTC)

Hmmm, I will check if we have a policy for that. --Tobias1984 (talk) 17:03, 11 July 2013 (UTC)

This property is becoming increasingly important. Is there anyone who opposes applying the resolution arrived at for disease-ontology-id Property_talk:P699 to this one? One way or the other, identifier schemes used for both of these ontologies (and the many other ones just like them) should really be treated the same way in wikidata. Lets resolve this and move on.. --I9606 (talk) 20:28, 12 October 2015 (UTC)

 Strong support I would very much like the prefix to be part of the identifier. Currently, when GO terms are added in our bot efforts the identifier, as it is provided by the original source. is preprocessed (ie the prefix is removed). This feels a bit hackish. In the documentation from the source http://geneontology.org/page/spatial-information-annotation-extensions the prefix is used. @Tobias1984: what is the policy here? --Andrawaag (talk) 19:35, 24 November 2015 (UTC)

 Support I think that all identifiers should carry the prefix if they have one. Makes it easier to immediately see what an ID is about. Sebotic (talk) 08:48, 26 November 2015 (UTC)

The property defines what it's value is about. For instance, the string "a7389752-9e5d-406d-9a02-9141600e4315" has no meaning, but in the context of MusicBrainz artist ID (P434) it is the identifier of the famous musician. Therefore I prefer in general to not duplicate the identifier type in the identifier, unless there is a strong reason. (For an exception to this general rule see for instance my comment on InChI (P234).) Toni 001 (talk) 12:22, 16 September 2019 (UTC)

 Support It doesn't make sense for identifiers to not have their prefix. Emitraka (talk) 17:40, 30 November 2015 (UTC)

 Oppose The Gene Ontology (Q135085) can be downloaded in the RDF/XML (Q48940) format from here (file go.owl). Therein identifiers like [1] are used. If the prefix "GO:" is not embedded in the identifier then we can have an formatter URI for RDF resource (P1921) of "http://purl.obolibrary.org/obo/GO_$1". Toni 001 (talk) 12:13, 16 September 2019 (UTC)

 Oppose prefix has to go into formatter. Currently the prefix is "GO:", but e.g. http://purl.obolibrary.org/obo/GO_0005773 has a prefix "GO_". CV213 (talk) 05:56, 2 March 2024 (UTC)