Naming Conventions

Revision as of 21:50, 30 January 2017 by Mrijanrimal (talk | contribs)
Jump to: navigation, search

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".


  • organize information on the topic into subsections. for each subsection, include a brief description / overview, with links to articles that provide details

Subsection 1

Subsection 2

Subsection 3

Back to Parent

This article is part of the topic *topic name, as listed on main page*

Additional Resources

  • list here other articles related to this topic, with a brief description and link