From a6d0a870ae1308b7b7d097b55540422e12300e2a Mon Sep 17 00:00:00 2001
From: Jover Lee <joverlee521@gmail.com>
Date: Wed, 27 Nov 2024 13:17:44 -0800
Subject: [PATCH] data-formats: Strongly word preference for TSVs

Recommended by @genehack in review

<https://github.com/nextstrain/docs.nextstrain.org/pull/238#discussion_r1861121872>
---
 src/reference/data-formats.rst | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/reference/data-formats.rst b/src/reference/data-formats.rst
index 359201e..2db1329 100644
--- a/src/reference/data-formats.rst
+++ b/src/reference/data-formats.rst
@@ -8,7 +8,9 @@ Data formats
 TSV
 ===
 
-Nextstrain generally uses TSV files for metadata.
+Nextstrain strongly prefers using TSV files for metadata even though Augur commands support other delimiters as inputs.
+If you are using other formats, we recommend using :doc:`augur curate passthru  <augur:usage/cli/curate/passthru>` to convert them to TSV.
+
 Nextstrain tools and workflows produce `RFC 4180 CSV-like TSVs <https://datatracker.ietf.org/doc/html/rfc4180>`__.
 
 When using `csvtk <https://bioinf.shenwei.me/csvtk/>`__