Main Menu

Powered by <TEI:TOK>
Maarten Janssen, 2014-

TEITOK Help Pages

Backups and Versions

In TEITOK documents are individually edited, potentially by various people, and in such a setting it is easy for error to slip in, and very hard to spot unwanted changes once introduced. To help in resolving problems, TEITOK makes a backup of edited files so that a file can be reverted to an earlier version.

In order not to put too heavy a load on the server disk space, only one backup copy is saved per day, which is always made prior to the first change of that day. So the backup of, for instance, the 12th of June 2014 will be version of the file saved on the 12th of June, which makes it technically speaking the version of the file before the 12th of June. The date of the current version is determined by the file modification timestamp, and in principle, the date of the current version should always be identical to the date of the last backup.

It is possible to revert back to one of the prior backups of a file, depending on when unwanted changes started occurring. In order to revert, select a backup of a certain day by clicking on "Recover a previous version of this file" and select the desired date (the option to recover only appears if there is at least one backup on file). This will first show the backup, after which you can select to reinstate that backup. Reinstating a backup will first save the current file as the backup for the next day (to allow undoing the change), and then overwrite the XML file with the selected previous version.

Version Differences

To help understand what has changed between versions, TEITOK offers a token-based version comparison. This comparison lists all the tokens for which there are differences between the two versions, and also list what these changes are. So for instance, it will state that in token w-45, the part-of-speech tag was changed from "V" to "P". The token can be directly edited by clicking on the ID.

Since tokens can be joined, split, inserted, or deleted, the system verifies that the text-content of the token has not changed. Tokens that do not directly matched between the two versions are shown with their raw XML value; when the system cannot resolve mismatching tokens, the system will stop and only report the last two tokens of each version.

Back to index