Ieboilsave

ieboilsave is is still in it is beta version, meaning that the current version is still a very early version that we are using for experimentation. The beta version still works and can be used, however, it might not yet be very useful and new version might include dramatic changes. This article describes what the intended use case is, but all functionality might not yet be implemented.

This article is means to describe use cases, work flow and the reasoning used when developing the commands. For instructions on how to use the command specifically in Stata and for a complete list of the options available, see the help files by typing help ieboilsave in Stata.

Intended use cases

The use case is very similar to ieboilstart as both commands help the user by including a lot of best practice boilerplate code without having to type it up manually. Instead of running boilerplate code in the very beginning of a master dofile as ieboilstart does, ieboilsave is meant to be run immediately before saving a data set.

ieboilsave runs test that are a good practice to run each time before you save a data set, and it stores meta infomration about your data set, when it was last saved etc. attached to the data set using Stata's built in char command.

The tests are meant to make sure that no edits done to the code alters that the data set

Intended Work Flow

Describe work flow here (remove if obvious from use case)

Instructions

These instructions are meant to help you understand how to use the command. For technical instructions on how to implement the command in Stata see the help files by typing help commandName in Stata.

Describe best practices related to this command here.

Reasoning used during development

Describe any non obvious decisions made during development of this command. This can help explain restrictions and requirements

Back to Parent

This article is part of the topic ietoolkit