Project Storage with Respect to Visio and SVG Files

Recommendations

1. As mentioned above, it is possible to disable the SVG creation until it is really needed (when the diagram has been released to 3D).

2. There is a setting to control whether to use binary Visio files or XML format Visio files. XML format requires much more storage space, so make sure to use the binary format.

3. There is a ‘Keep session files’ setting that will determine whether the old versions of the Visio and SVG files will be kept during each SaveWork or not. With this setting you can balance between ‘more data management capability & more storage space required’ or ‘less data management capability & less storage space required’ as is described below:

   • With this setting set to True there is a possibility to backtrack the Dabacon session and access the specific Visio/SVG file versions related to that particular session. The drawback here is, of course, that it may take a significant amount of storage space to save the related files for all sessions.

   • With this setting set to False only latest versions of the Visio/SVG files will be kept. This means that backtracking a Dabacon session will not give access to the corresponding Visio/SVG files. However, storage space requirements will be less demanding.

   • When ‘Keep session files’ is set to True, and sessions are to be merged, then select Admin Tab > Admin Tools > Project Maintenance > Clean Old Session Files to get rid of the corresponding Visio/SVG files. This can be an approach where there is a possibility to backtrack changes during a period. Merge and clean the sessions and continue from there.