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

uta schema overhaul #204

Open
reece opened this issue Mar 14, 2017 · 4 comments
Open

uta schema overhaul #204

reece opened this issue Mar 14, 2017 · 4 comments
Labels
keep alive exempt issue from staleness checks

Comments

@reece
Copy link
Member

reece commented Mar 14, 2017

This epic is an umbrella for UTA schema overhaul plans

Goals:

Admin changes

  • enable schema migrations. This amounts to choosing between keeping SA and using Alembic, or ditching SA (and using direct SQL) with yoyo migrations (presumably).
  • use py models?

Updated schema elements

  • create index exon_set_alt_ac_method_idx on exon_set(alt_ac, alt_aln_method);
  • exon sets defined on sequence digests (rather than accessions)
  • sequence aliases (wholesale import from seqrepo?)
  • exon-set-relationships view: exon-exon relationships based on digests
  • store multiple alignments (currently, only 1 aln per <tx_ac, alt_ac, alt_aln_method>

New schema and content

  • cds se on all coding exon sets
  • digest table (linked to exon set, I think)
  • assembly data
  • LRG data
  • exon set digests as PK
  • alignment digests as PK
  • gene-tx table
@reece reece changed the title uta schema overhall uta schema overhaul Jan 5, 2023
Copy link

github-actions bot commented Dec 7, 2023

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale Issue is stale and subject to automatic closing label Dec 7, 2023
Copy link

This issue was closed because it has been stalled for 7 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 15, 2023
@reece reece reopened this Feb 19, 2024
@reece reece added resurrected and removed stale Issue is stale and subject to automatic closing labels Feb 19, 2024
@reece
Copy link
Member Author

reece commented Feb 19, 2024

This issue was closed by stalebot. It has been reopened to give more time for community review. See biocommons coding guidelines for stale issue and pull request policies. This resurrection is expected to be a one-time event.

Copy link

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale Issue is stale and subject to automatic closing label May 20, 2024
@jsstevenson jsstevenson added keep alive exempt issue from staleness checks and removed stale Issue is stale and subject to automatic closing resurrected labels May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
keep alive exempt issue from staleness checks
Projects
None yet
Development

No branches or pull requests

2 participants