Dear All,
When i saved a document as versioning in Laserfiche.
How does it saved in the database?
1. as incremental
2. does it saved the document as a new one every time i put a version on it.
thanks in advance
Hi Iqbal,
The Laserfiche volumes house images and electronic documents, and within the volumes new versions of a document are kept as separate files linked together based on references in the database. As for other components that make up a Laserfiche document (such as the different types of annotations, field values, tags, signatures, etc. that are all housed in the database), some items are version specific and others may not be.
To better answer your question it would help us to understand what you are trying to accomplish with regard to document versions. What are you trying to do here?
Hello Kelsey,
Our aim is to know the space requirement for the database for versioning purpose.
If the versioning is incremental this means to us that space requirement will not be that much, however, if there is a separate file for each version, then we need to much more space.
can you just confirm me whether or not it is like this or not?
thanks in advance
Thanks for the extra info, Iqbal. To provide you with the most complete answer regarding space considerations, I need to address both the database and the volumes.
The volumes hold the file itself - its pages and images - while the database contains information about the file - its metadata, annotations, etc. How the changes in the new version affect the volumes and database depends on the kinds of changes made. For example, if metadata was changed, then the old and new versions of that metadata will be saved within the database, and the volumes will remain unaffected (because no changes were made to the document itself). On the other hand, if the document's text was changed, then an entirely new document is saved within the volumes; however, the only information added to the database is the version history that you see in the metadata - description of what changed, comments, and the link to the appropriate document in the volumes.
Therefore, changes made direcly to the document will create a separate file for each version within the volumes, with a small amount of indexing information added to the database. Changes made to information associated with the document will create incremental updates solely within the database.