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

Workflow for adding updated refseq alignment data #236

Closed
soensz01 opened this issue Nov 12, 2021 · 4 comments
Closed

Workflow for adding updated refseq alignment data #236

soensz01 opened this issue Nov 12, 2021 · 4 comments
Labels
closed-by-stale stale Issue is stale and subject to automatic closing

Comments

@soensz01
Copy link

I believe there have been similar questions and I'm uncertain if there was a clear recommendation about how one would go about adding new transcript data into uta for use with the hgvs module such as the data from here:
https://ftp.ncbi.nlm.nih.gov/genomes/all/annotation_releases/9606/105.20201022/

Will proper functionality require that changes to the transcript sequences as well as the alignment data be available within the seqrepo data as well?

Thanks for any advice

Copy link

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 Nov 28, 2023
Copy link

github-actions bot commented Dec 5, 2023

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 5, 2023
@reece reece removed stale Issue is stale and subject to automatic closing closed-by-stale labels Dec 8, 2023
@reece reece reopened this Dec 8, 2023
Copy link

github-actions bot commented Mar 8, 2024

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 Mar 8, 2024
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 Mar 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-by-stale stale Issue is stale and subject to automatic closing
Projects
None yet
Development

No branches or pull requests

2 participants