Built-in SQLite to be used as a backend database, However this is not required for the operation of the archive but provides support for operations such as searching the archive for which a database is ideal.
Maintain data integrity of the archive by providing integrated integrity systems to guard against accidently corrupting the archive.
Follows an open design approach in that the storage format is open giving the ability of other tools to be integrated into the archive system.
Image information is organised in a flat file system that is directly viewable by a text editor using XML and CSV file formats
Optionally a SQLite database can also be used as an Information management system which can augment the flat file structure.
The archive is designed to be simple in design and to use. It consists of archiving core that provides the basic archiving functions but in addition, takes input and provides output from optional external components to provide a tailored archiving solution that can be extended into a complete achieving system.
The Archive takes a simple design approach that many source code repositories take, in that it uses the host operating system file system as the primary storage for the images in the repository. The archive is organised in folders that reflect the images capture date or the date added to the archive. The archive repository consists of a simple file hierarchy based on year, month, and day. These are created has required depending on date of the image.
So a typical archive will have a root or main folder and sub-folders for each year. Under the year will be folders with the date simply encoded into the folders name. By default the image file name will be the standard format the camera manufacture uses. This however can be configured to be renamed if required.
Image information is also stored in a flat file system that is directly viewable by a text editor using XML and CSV file formats. Optionally an SQLite database can also be used as an Information management
Built-in SQLite to be used as a backend database.