diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index e40f4a60ba0c32e38bc1c94427a85d0d9a92a425..1f341df9be55ff88f75df1403410b78395cd7a19 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -130,6 +130,23 @@ If you want to use information within the `file_id` to name outputs in your `scr
 ```
 and use the `file_prefix` variable.
 
+This also means that channel emitting `path` item should be transformed with at least the following map function:
+
+```
+.map { it -> [it.simpleName, it]}
+````
+
+for example:
+
+```
+channel
+  .fromPath( params.fasta )
+  .ifEmpty { error "Cannot find any fasta files matching: ${params.fasta}" }
+  .map { it -> [it.simpleName, it]}
+  .set { fasta_files }
+```
+
+
 The rational behind taking a `file_id` and emitting the same `file_id` is to facilitate complex channel operations in pipelines without having to rewrite the `process` blocks.
 
 ### dealing with paired-end and single-end data
diff --git a/src/nf_modules/bowtie2/main.nf b/src/nf_modules/bowtie2/main.nf
index 1dc0780d52dc6b5118022a91fdf2b5c9c9f73e59..efd0ceb358cce419572e3a2a33a50713a32ad912 100644
--- a/src/nf_modules/bowtie2/main.nf
+++ b/src/nf_modules/bowtie2/main.nf
@@ -46,7 +46,7 @@ process mapping_fastq {
   tuple val(file_id), path(reads)
 
   output:
-  tuple val(file_id), path("*.bam"), emit: bam
+  tuple val(), path("*.bam"), emit: bam
   path "*_report.txt", emit: report
 
   script: