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

populate-jbrowse2: add refNameAliases when available #30

Open
nathanweeks opened this issue Sep 30, 2023 · 2 comments
Open

populate-jbrowse2: add refNameAliases when available #30

nathanweeks opened this issue Sep 30, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@nathanweeks
Copy link

Could the populate-jbrowse2 subcommand support per-assembly refNameAliases file (like the jbrowse add-assembly --refNameAliases option: https://jbrowse.org/jb2/docs/cli/#jbrowse-add-assembly-sequence)?

I'm not entirely sure what the CLI would look like. One suggestion is perhaps populate-jbrowse2 --refNameAliases_dir=<path>, where <path> is a path to a directory of refNameAliases TSV files named, e.g., <name>.txt; for each reference assembly name that is encountered in the yml config files, if <path>/<name>.txt exists, then a refNameAliases property is added to the output config.json. Could be other ways to implement this too.

@nathanweeks nathanweeks added the enhancement New feature or request label Sep 30, 2023
@adf-ncgr
Copy link
Contributor

adf-ncgr commented Oct 4, 2023

Thanks @nathanweeks and sorry for the delayed response. It's a good idea, my initial reaction is that we ought to have a standardized (but optional) file resident in the datastore that iff present autocontent would just pass along as a URL for the --refNameAliases option value. I think that's pretty similar to what you suggested, except that there would be no option on the populate-jbrowse2 subcommand, it would just make it happen depending on the state of the datastore content. Would that work for your intended uses?

@adf-ncgr
Copy link
Contributor

adf-ncgr commented Oct 4, 2023

PS. IIRC, you can have a single tab-delimited file with multiple aliases per record, but if that isn't the case having a directory for these files as you suggested might be needed

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

No branches or pull requests

2 participants