Jay and Chloe,
I'm not sure what the problem is, but here are some further things you can try:
1. Use "incognito" mode in Chrome to access Phinch - sometimes removing the browser cache via anonymous browsing will fix the spinning wheel
2. Check the line breaks on the converted file using a text editor such as TextWrangler or BBedit - they should be Unix line feeds (LF), NOT carraige returns (CRs - this sometimes gets changed if you open a tab-delimited file in Excel)
3. Try making a new BIOM file using the OTU map that gets outputted from the pick_otus.py worflow. An example command would be as follows:
make_otu_table.py -i final_otu_map_mc2.txt -o otu_table_mc2_w_tax.biom -t rep_set_tax_assignments.txt
(Your BIOM file may be outputted in HDF5 format if you're using QIIME 1.9 - so use the "head" command to look at the text file output)
4. Get access to QIIME 1.8 somehow, and execute the above make_otu_table.py command - this will avoid the HDF5 BIOM 2.0 file issue entirely. I use MacQIIME on my local laptop, and it is super easy to switch back and forth between QIIME versions (basically you just rename folders and refresh the terminal windows). Amazon EC2 and many University HPC systems also support several QIIME versions with different modules.
On QIIME 1.8, after you make the OTU table you will then have to add the metadata before loading the JSON-formatted BIOM file into Phinch:
biom add-metadata -i otu_table_mc2_w_tax.biom -o otu_table_mc2_w_tax_and_metadata.biom -m sample_metadata_mapping_file.txt
Let me know if any of these suggestions does the trick! And if you find out what was the issue with QIIME 1.9 files, please let me know too - many people seem to be encountering the same error.
Thanks,
Holly