Arabidopsis-Information-Portal/deploy-community-tracks

Application may need to support namespacing on the tracks

Opened this issue · 0 comments

If we end up automatically deploying Jbrowse config files generated by the application to Araport, we need to ensure that the track descriptions that show up in Jbrowse are distinguishable. We namespace the files that are generated with a combination of Cyverse username and Agave job ID, but not the tracks. Let's explore a solution in comments.