The genomics workspace app sequences table is gigantic, and only keeps growing based on the way the schema was built. Since it's creation, updates to the NCBI BLAST binaries have included a tool that should replicate the use case filled by the sequences table, without the overhead.

Before we can deprecate the table and replace the functionality, we need to:

• Confirm all of the places and ways the table is used
• Confirm that we can recreate functionality
• determine if there are changes needed in order to make the new method work (ex: do the seq names work?)
• Test swapping out the methods in the code
• Confirm that it is working
• Clear out the table.

I have some other questions that @g8tor can probably answer best, like if we can keep the sequences class and stuff downstream, but change the class and models to reflect the new way of calling up fastas. The other question is houw tough it would be to build in some limits so we don't try to background stream GB sequences to the client. Maybe a note saying this sequence is to big to see in the browser, click here to save it to your machine?