Editor Checkout, Timestamp, and Editing
The following issue may occur when checking in content.
Issue: Edit changes are not saved when the files are checked in, history is not modified to reflect the edit. Messages indicate that the save was successful.
Reported for: FrameBook and XMetaL tools. True for all editor checkin/checkout tools.
Technical Explanation: In the EntIdMap file written in the checkout directory with each document checked out, the GetDoc adapter stores the system time where the Adapter is running, typically the client. GetDoc creates one file (chunk) for each object exported. The checked‐out files are saved with the timestamp of the system where the files are written. The PutDoc adapters compare the time stored in the EntIdMap to the file stamp time of the ʺfile chunksʺ. Some editors use a GetDoc adapter that “concatenates” the file chunks into a single document and a corresponding PutDoc adapter that splits the document into file chunks during the check in process. Only the chunks that were modified (or newly created) are written back to the file system. When the system time on the client computer where the adapters are running does not match the system time of the host computer where the mapped drives are installed, edit changes may never be saved or may always be saved.
Resolution: Time‐sync the host computer drive and the Contenta client system(s) that use those drives. There is system software available to keep computers on a network synchronized so that they all have the exact same system time.
If you use mapped drives, be certain to ensure the time on your clients is synchronized with the time on the host system(s) that contains your checkout directories. If the time is not the same, edits may not be saved (or may always be saved).
Contenta does not detect this problem and does not display an error message; message is that files were checked‐in successfully.