Skip to content

Commit e25132f

Browse files
committed
implement Jonjab's feedback
1 parent 2d2191d commit e25132f

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

datamgmt_manage.qmd

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ As you collect your data, if using pre-existing data sources, we strongly recomm
1212
- Go back to the original source and the right version of the data
1313
- Correctly attribute/cite the data sources when you project
1414
- Reach out to data creators and ask for potential clarifications you might need to correctly interpret the data
15-
- Inquiry for any data updates at a later date
15+
- Inquire about potential data updates at a later date
1616

1717

1818
## Keep raw data raw
@@ -49,11 +49,12 @@ In the top-level folder, we also recommend you write a README to explain your pr
4949
Develop naming conventions for files and folders:
5050

5151
- Avoid spaces (use underscores or dashes)
52-
- Avoid punctuation or special characters
53-
- Try to leverage alphabetical order (e.g., start with dates: 2020-05-08)
52+
- Avoid any other punctuation or special characters
53+
- Try to leverage alphabetical order used by default by computers to sort files (e.g., start with dates in the [ISO format](https://en.wikipedia.org/wiki/ISO_8601): YYYY-MM-DD, as example 2020-05-08)
5454
- Use descriptive naming (lite metadata)
55-
- Use folders to structure/organize content
56-
- Keep it simple
55+
- Avoid using upper case, or at least be consistent in usage (e.g. Folder's name start with upper case, files with lower case)
56+
- Use folders to structure/organize content, but avoid more than 3 levels of nesting
57+
- Keep it simple, e.g. no path longer than 255 characters
5758
- Make it programmatically useful:
5859
- Useful to select files (Wildcard *, regular expression)
5960
- But don’t forget Humans need to read file names too!!

0 commit comments

Comments
 (0)