Hello Morgan,
There indeed could be something awry with the mapping/sampleIDs.
You want your sampleIDs to be something like AFF1G, right? Is this what you have in your mapping file?
Step 1 and 2 are fine I think.
You may need to filter out the unjoined reads before step. To get rid of the unjoined data (first make sure you have reasonable counts of joined data, e.g. make sure the joined files are much larger than the unjoined files), here's an example Linux command to do so:
find input_dir/ -name "fastqjoin.un*" -print -exec mv {} output_dir/ \;
where input_dir is the folder containing all of the subfolders with your joined reads (i.e. multiple_joined/ above, but depends upon where you are running the command), and output_dir will be where the files will be dumped to (you want to create this folder before running the command). After doing this, you should just have the joined fastq files remaining.
I don't think you need to do step 3, since the barcodes are already in R2.
Step 4 is where you might have hit a snag in the naming of the samples. I'd recommend getting rid of the unjoined data above, and rerunning multiple_split_libraries_fastq.py using the multiple_joined/ folder as input. If you add -w, it will print the command instead of running it, and you can add:
-w > slf_command.txt
to write the command it's generating to a text file. I would make a copy of this text file, and then edit it, and look for the --sample_ids section at the end, and make sure they match the desired SampleIDs in your mapping file. You may have to fix these by hand. Then you can copy the full command from the text file, and run it directly.
See this thread for an example of editing that multiple_split_libraries_fastq.py command:
For chimera checking, it may not be necessary since there are some filters built in that likely capture the chimeras (filtering singletons, filtering sequences that do not align to the template 16S alignment). If you do want to do chimera checking, I would follow this approach:
http://qiime.org/tutorials/chimera_checking.html#usearch-6-1which means you would do chimera checking before doing open reference OTU picking with usearch61 (or the download the software vsearch,
https://github.com/torognes/vsearch, rename it usearch61, and use it instead if you run into 32-bit memory issues).
Whether you do or skip chimera checking, I'd recommend figuring out if everything is okay once you have completed the open-reference OTU picking. You should be able to get the OTU table with:
biom summarize-table -i OTU-TABLE.biom -o table_stats.txt
and you will be able to see sequence counts per sample and if the sampleiDs look correct.
-Tony