Recording which standard procedures and conventions your project will use to name data-related files can help everyone involved to use the same scheme and maintain consistency. Consider including a README.txt file in your data folder that explains your naming convention along with any abbreviations or codes you have used. e.g. Make sure names are relatively short, avoid spaces and special characters. You can use underscore characters, and consider using unique identifiers for the samples/experiments. You can consider adding the date in YYYYMMDD format.
There is no single best protocol for file naming. The most important thing is to use the naming convention you choose consistently across the project.
From the FAIR data wizard:
Recording which standard procedures and conventions your project will use to name data-related files can help everyone involved to use the same scheme and maintain consistency. Consider including a README.txt file in your data folder that explains your naming convention along with any abbreviations or codes you have used. e.g. Make sure names are relatively short, avoid spaces and special characters. You can use underscore characters, and consider using unique identifiers for the samples/experiments. You can consider adding the date in YYYYMMDD format.
There is no single best protocol for file naming. The most important thing is to use the naming convention you choose consistently across the project.
e.g., instrument_[location|platform]_YYYYMMDD[hh][mm][ss][_extra][_cor#].ext