File versioning
Comic: Jorge Cham. "notFinal.doc"
Version control is a method used to track file or file set changes over time so that you can recall older versions at a later time.
  • Version control records changes (additions, deletions, replacements) of individual files, tracks updates, and allows branching of projects that may be later integrated into the parent project.
  • File versioning can be as simple as using file naming conventions like suffixes *_v1, *v2, *vn, or you could use a version control software (VCS).
  • Version control software allows multiple people on a team to work together on the same project at the same time. It manages changes to all types of text-based files, like scripts and web pages as well as some proprietary digital formats.

Advantages to Version Control Software

There are three advantages to version control software:

  1. Infinite undos: VCS allows users to revert to a previous version of a file or file set to restore or recover a previous state of a program application or website. This allows you to restore accidentally deleted or overwritten files in a project, or to restore file sets from a prior version save.
  2. Branching and experimentation: This is powerful as it allows you to test out new features in programming code or branch out on a different path without affecting your collaborator's work in the production code. Later, your branch can be merged in with the production, saved, or discarded as necessitated.
  3. Collaboration: Collaborators can work locally on the file while the VCS handles the tasks of merging changes and keeping the files and directory trees in sync. The VCS also promotes accountability, tracking who's made which changes and when, so any questions about the changes can be followed up with the appropriate person.
     

Software Tools

Below are a some version control software and and file sharing tools used at Harvard. It is important to note the following:

  1. Since Harvard does not necessarily host each of these products, at the close of a project, be sure to retain a copy of the file sets to be saved in the Harvard or sponsored research archive at the close of the project, they must provide Harvard with a copy of the files.
  2. If your files contain any proprietary or confidential information, you must store these in a Harvard Security Level 4 or 5 certified environment.

File Sharing Platforms