So if I understand blast-results.js correctly (and I might not), it uses the title field in blast_blastdb to build the URL string that will display the blast results in the genome browser (jbrowse/apollo). The title field value is (I think) automatically generated from the fasta file path in manage.py addblast. Usually we can add in just the file name, and, if you're in the i5k root directory, you're good, but it is not unreasonable to assume that sometimes we'll forget that and use the full path when we're loading the data. That breaks the URL generated in blast-results.js, since it's looking for a file with the extra file path info loaded in.
Is there a more elegant way to handle this? I guess we could update manage.py addblast to also add the title - or instead perhaps blast-results.js could strip the path info from the fasta url path info?
So if I understand blast-results.js correctly (and I might not), it uses the title field in blast_blastdb to build the URL string that will display the blast results in the genome browser (jbrowse/apollo). The title field value is (I think) automatically generated from the fasta file path in
manage.py addblast. Usually we can add in just the file name, and, if you're in the i5k root directory, you're good, but it is not unreasonable to assume that sometimes we'll forget that and use the full path when we're loading the data. That breaks the URL generated in blast-results.js, since it's looking for a file with the extra file path info loaded in.Is there a more elegant way to handle this? I guess we could update
manage.py addblastto also add the title - or instead perhaps blast-results.js could strip the path info from the fasta url path info?