36 Version Control
Previous Lesson
Lesson 7 of 17
Consider how to document different versions of files clearly. Planning in advance makes it easier to be consistent. Using terms like “final,” and then having to edit changes into the “final” version can be problematic.
You can use version numbers in filenames (e.g., _v1); add a date to a filename; adopt a version control tool or software; or keep a version control history table where versions, dates, and file changes are recorded.
Consider the following when planning for version control and data storage:
- How many versions will you keep?
- Are there important milestones for major and minor revisions?
- Do you need to keep all minor revisions in the longer term?
- Do you want to differentiate between major and minor revisions?
- Record important relationships between files
- If you have code, note for which data it is used.
- If you are using software into which you import data (e.g., qualitative data analysis software like NVivo), which versions get imported, and how are files structured within the tool?
- How can you synchronize files if they are stored in multiple locations?
- Consider using a single location for master copies.
- Are you using a tool with built in versioning features (e.g., SharePoint, DropBox, Git)?
- How can entries or edits by multiple team members be tracked?
