Session storage scheme is incredibly versatile and natural

TSP files are useful to save your work, but may I suggest a “session” scheme like that found in Capture One which is very popular with those users. A session may be created and named by the user for an event, trip, time passage, anything. Each session has a directory structure to store images, RAWS, and a user customizable folder structure to segregate and organize images, for example: Capture, Selects, Trash, Complete, Publish, etc. A binary database file stores all adjustments for the images on the fly, so there is no waiting to save TSP files at the end of an edit. The entire session can be easily moved within a directory structure, archived, or moved across a network to another system. When the program starts, the last session is automatically loaded and saved automatically every time the program is terminated. When you open Capture One, it loads exactly where where you left off. Each time an adjustment is made, it is stored in the database file. Nothing is ever lost, even if the program crashes. Images can be exported and imported along with their adjustments in a folder with the raw image and TSP like file.

The user can move the picture between folders as their workflow dictates. Having the ability to organize a load of images greatly simplifies workflow. The user can customize the session template to provide the desired folders. Recipes can apply adjustments and move folders automatically between folders.

Sessions are very versatile, nimble, and a natural method for imaging workflow. They give users a lot of functionality without a complex catalog system, and so naturally functional, users don’t need to consciously save their work, or remember to save all their TSP files which can take some time.