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

KEGG Brite (BR) hierarchy example does not resolve #1185

Open
cmungall opened this issue Sep 11, 2024 · 4 comments
Open

KEGG Brite (BR) hierarchy example does not resolve #1185

cmungall opened this issue Sep 11, 2024 · 4 comments

Comments

@cmungall
Copy link
Contributor

https://bioregistry.io/registry/kegg.brite

Example

kegg.brite:ko00071

goes to https://www.genome.jp/kegg-bin/get_htext?-p+/kegg/brite/br+brko00071

"Not found"

@cmungall
Copy link
Contributor Author

In this case, ko00071 is part of BRITE and represents the grouping "Fatty acid degradation"

There are a variety of ways to see this in different contexts, e.g. this URL

https://www.genome.jp/brite/htext=ko00001.keg&query=ko00071

shows this hierarchy

  • 09100 Metabolism
    • 09101 Carbohydrate metabolism
    • 09102 Energy metabolism
    • 09103 Lipid metabolism
      • 00061 Fatty acid biosynthesis [PATH:ko00061]
      • 00062 Fatty acid elongation [PATH:ko00062]
      • 00071 Fatty acid degradation [PATH:ko00071]
        - K00626 ACAT, atoB; acetyl-CoA C-acetyltransferase [EC:2.3.1.9]

Where you can see the BRITE ko in a pathway context:

https://www.genome.jp/pathway/ko00071

However, I am not sure there is a consistent way to resolve to a BRITE ID that is not in some other context

@bgyori
Copy link
Contributor

bgyori commented Sep 11, 2024

It looks like there are two issues compounded here:

  • The resolver URL is not quite right: if we update it to https://www.genome.jp/brite/$1 it can resolve various IDs that I found
  • The example ID might have been removed and should probably be replaced by one that works, e.g., ko03041

@bgyori
Copy link
Contributor

bgyori commented Sep 11, 2024

@cmungall for context, I wrote my comment before your second comment showed up.

I admit I am confused by the situation with BRITE and KEGG identifiers in general. Would updating to the URL pattern to https://www.genome.jp/brite/$1 and changing the example ID to something that is definitely in scope for BRITE, e.g., br08614 or ko03041 (which both resolve correctly at https://www.genome.jp/brite/$1) make sense?

@cmungall
Copy link
Contributor Author

Thanks, I don't have the answers yet....!

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

No branches or pull requests

2 participants