Skip to content

Do you have a standard procedure in place for folder and file naming? #30

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
simonrolph opened this issue Apr 4, 2024 · 0 comments
Open
Labels
FAIR Relating to the FAIR principles

Comments

@simonrolph
Copy link
Collaborator

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

@simonrolph simonrolph added the FAIR Relating to the FAIR principles label Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FAIR Relating to the FAIR principles
Projects
None yet
Development

No branches or pull requests

1 participant