From c5e299585a8dd632f4dbfd42e84ccc267c10d54c Mon Sep 17 00:00:00 2001 From: bvarner-ebi <95643797+bvarner-ebi@users.noreply.github.com> Date: Mon, 21 Aug 2023 13:50:38 +0100 Subject: [PATCH] Update guidance on adding URL dbxrefs (editing_guidelines.md) Update guidance on adding URL dbxrefs (editing_guidelines.md). --- docs/editing_guidelines.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/editing_guidelines.md b/docs/editing_guidelines.md index f219482dc..c50c49ca4 100644 --- a/docs/editing_guidelines.md +++ b/docs/editing_guidelines.md @@ -113,7 +113,9 @@ ORCID identifiers may also be used when the only available source for an asserti **Technical details of adding a cross-reference using Protégé**: -For CURIEs and ORCIDs: In the "Create Annotation" window, select the annotation property **database_cross_reference**. +For CURIEs, ORCIDs: In the "Create Annotation" window, select the annotation property [**database_cross_reference**](http://www.geneontology.org/formats/oboInOwl#hasDbXref). +For adding URLs to text definitions or synonyms: In the "Create Annotation" window, select the annotation property [**database_cross_reference**](http://www.geneontology.org/formats/oboInOwl#hasDbXref). +For adding URLs to axioms that are NOT text definitions or synonyms: In the "Create Annotation" window, select the annotation property [**source**](http://www.geneontology.org/formats/oboInOwl#source). For CURIEs: Enter the CURIE, using the [bioregistry OBO context](https://bioregistry.io/context/obo) prefix ([link to prefixmap](https://github.com/biopragmatics/bioregistry/blob/main/exports/contexts/obo.context.jsonld)), as a Value on the "Literal" tab. Leave Datatype empty. @@ -121,13 +123,10 @@ In cases where more than one CURIE is available for a resource, either is accept For ORCIDs: Enter the ORCID as an IRI in the IRI field on the "IRI Editor" tab, for example `https://orcid.org/0000-0002-7356-1779`. -For URLs: In the "Create Annotation" window, select the annotation property **'see also'** (`rdfs:seeAlso`). Enter the URL as a literal string with Datatype `xsd:anyURI` selected. -DO NOT use database_cross_reference with a value that is a URL. +For URLs: Enter the URL as a literal string with Datatype `xsd:anyURI` selected. To restate, in all cases above except ORCIDs, the values are entered as literal strings. An ORCID MUST BE entered as an IRI. -The above instructions apply whether the cross-reference is added to another annotation (e.g., annotating a text defintion or comment) or adding to the overall class (i.e., not an annotation of another annotation). - ## Term contributors When adding an ORCID to identify a term contributor, in the "Create Annotation" window, select the annotation property **dcterms:contributor**. The ORCID is still entered as an IRI on the “IRI Editor” tab.