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

Prioritization of Steps in Converting Molecular Events #296

Open
3 tasks
ukemi opened this issue Oct 13, 2023 · 7 comments
Open
3 tasks

Prioritization of Steps in Converting Molecular Events #296

ukemi opened this issue Oct 13, 2023 · 7 comments
Assignees

Comments

@ukemi
Copy link

ukemi commented Oct 13, 2023

  • Will Reactome accept the strategy of assigning Molecular Functions as enablers to Reactome Reactions that get translated as Molecular Events.
  • If so, can we provide a flat file as an input to make the changes in Reactome automatically.
  • How do we prioritize which pathways to curate?
    - [ ] signaling because we already did the proof of principle
    - [ ] Pathways with a small number of molecular events. @dustine32 will create a report.
    - [ ] Pathways with which a curator has expertise
    - [ ] Coordinated with existing GO-CAM curation workflow. In other words, if a curator is focusing on a pathway for curation, take on the Reactome pathway as well.
    - [ ] Create curation workflow documentation.
@dustine32
Copy link
Collaborator

Here is the report on number of molecular events in all Reactome pathway GO-CAMs. This was against the set of models currently loaded (commit d1e90f6) into noctua-dev. 8171 molecular events spread across 1263 pathway models:
reactome_all_mol_event_pathways.txt

I added some code to try also capturing any "individual" w/o any class (i.e., no rdf:type other than just OWL:NamedIndividual) but I'm not sure if it works as I couldn't find any GO-CAM node like this to test for. If anyone spots one of these, could you please report the pathway and reaction (or otherwise its individual ID)?

@ukemi
Copy link
Author

ukemi commented Oct 18, 2023

Thanks @dustine32. That's a long tail of pathways with only a few. Some of them will be covered as we continue the signaling pathways.

@ukemi
Copy link
Author

ukemi commented Oct 18, 2023

I put a copy of the report in a spreadsheet in the project Google folder.

https://docs.google.com/spreadsheets/d/1wSUrHy-FSxtaaBQFC90kWkmqOMvO2Tp8-Uu2GffBUq4/edit#gid=0

@dustine32
Copy link
Collaborator

For @huaiyumi, here is the list of molecular events by reaction:
reactome_all_mol_events.txt

@huaiyumi
Copy link
Collaborator

huaiyumi commented Nov 2, 2023

@dustine32 Do you think you can expand this file by adding the molecular events to the file like this one? https://docs.google.com/spreadsheets/d/1WxHvGZzf3tEX3GtCvSMGFRhCev4TaCuJLrPs_whDUNs/edit#gid=0
The data in column C and D are useful for us to curate.

@huaiyumi
Copy link
Collaborator

huaiyumi commented Nov 2, 2023

Oh, there are two files. I only downloaded the one reactome_all_moe_event_pathway. I guess the other has everything.

@deustp01
Copy link
Collaborator

@dustine32 Do you think you can expand this file by adding the molecular events to the file like this one?

That file is the one we used to identify events without specific molecularFunctions within the Reactome top-level domain of "signal transduction". A useful way to proceed might be to take the existing file, reactome_all_mol_event_pathways.txt and https://docs.google.com/spreadsheets/d/1wSUrHy-FSxtaaBQFC90kWkmqOMvO2Tp8-Uu2GffBUq4/edit#gid=0, and re-order it so all events that fall into each superpathway are grouped together. My hunch is that each such domain of biology will be enriched in a distinct set of problems (as signaling is in binding events that lack an enabler but for which enablers can often be inferred). If this is right, then the grouping will be really useful in dividing up the large re-annotation task into smaller, more narrowly defined tasks.

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

No branches or pull requests

5 participants