Difference between revisions of "Naming Conventions"
Mrijanrimal (talk | contribs) |
Mrijanrimal (talk | contribs) |
||
| Line 10: | Line 10: | ||
== Back to Parent == | == Back to Parent == | ||
This article is part of the topic [[ | This article is part of the topic [[Data Management]] | ||
== Additional Resources == | == Additional Resources == | ||
Revision as of 15:29, 3 February 2017
Impact Evaluation projects should follow a clear naming convention as all the files in the project will be used throughout the project duration. Since over the course of an impact evaluation project, personnel doing research, or on the field might change, it is very important to use a naming convention that not only you understand but someone looking at the files after years also understands.
Read First
Use the version control in Box/DropBox instead of naming the folders _v01, _v02, old, new, etc. Output tables, graphs, and documentations are an exception to this and it is good practice to date them. Instead of using versions, they should be dated for clarity. For example = "_2017June8" rather than "_v02".
Reasoning - 2 years down the road. ENdline, new-final-v2.
Guidelines
Here are some of the important guidelines to follow when naming files and folders in your impact evaluation folder:
Back to Parent
This article is part of the topic Data Management
Additional Resources
- list here other articles related to this topic, with a brief description and link