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

Ontobee should not be "hard-coded" for the links, but either go to the right location or use PURLs #44

Open
kltm opened this issue Sep 24, 2024 · 3 comments

Comments

@kltm
Copy link
Member

kltm commented Sep 24, 2024

To reproduce:

As we have been having Ontobee outages, and I can see this same information in AmiGO (and that's obviously under our control), I see no reason not to link to AmiGO with https://amigo.geneontology.org/amigo/term/ECO:0000501

In reference to
https://agr-jira.atlassian.net/browse/SCRUM-4463
https://agr-jira.atlassian.net/browse/AGRHELP-343

@kltm
Copy link
Member Author

kltm commented Sep 24, 2024

@pgaudet I'm not sure of a priority for this, but I think it would be good to get to at some point.
First pointed out by @sierra-moxon , I believe in reaction to the linked AGE issues above.

@kltm kltm changed the title Change from Ontobee to AmiGO for evidence code links Ontobee should not be "hard-coded" for the links, but either go to the right location or use PURLs Oct 2, 2024
@kltm
Copy link
Member Author

kltm commented Oct 2, 2024

Talking to @cmungall , if hard-coded, it should go to where the PURLs go; otherwise, get it recompiled.

@kltm kltm moved this to To do in Alliance software support Oct 2, 2024
@kltm
Copy link
Member Author

kltm commented Oct 4, 2024

Noting that ontobee is currently down again.

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

No branches or pull requests

1 participant