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

Database Persistence #7

Open
10 tasks
chrtannus opened this issue Oct 2, 2024 · 0 comments
Open
10 tasks

Database Persistence #7

chrtannus opened this issue Oct 2, 2024 · 0 comments
Assignees

Comments

@chrtannus
Copy link
Member

chrtannus commented Oct 2, 2024

For each successful query, save into MongoDB:

  • The network, including:
    • network ID
    • network name
    • network topology1
    • node and edge attributes1
    • node positions
  • The iRegulon results (motifs and tracks with their target genes and TFs, ranks, NES values, etc.) -- I don't think we need to save the TF view, since it's derived from the motifs and tracks.
  • Motifs/Tracks/Clusters selection, including the currently selected TFs (from the data tables).
  • The query parameters -- see Query iRegulon - predict regulators and targets #2 and Query the Metatargetome #3
  • The creation time and last access time

NOTE: I think the demo network doesn't need to be stored in Mongo. Just create it again every time from static or even in-memory data. Or if it's more convenient to load the demo data from the same DB, the network data does not need to be updated (e.g. with node positions) -- see #8.

Footnotes

  1. Maybe we don't need to save the network elements, because the network can be recreated from the results again when reloading the data. Either way, the persisted data must contain information about which Motifs/Tracks/TFs were used to create the network--we also need this information to restore the checked rows when loading the data tables. 2

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