How the Checkin Tool Works
As part of the FrameBookCheckin, the book, chapters, and/or graphics files are checked for changes.
The check-in process scans the selected book file and its corresponding chapter files for any new additions, modifications, or deletion of chapters and/or graphics. The EntIdMap file is updated and the tool reads the file and updates the Contenta objects and hierarchy accordingly.
- If an existing object’s editing state is YES, the object is updated. Only the modified files are checked-in. If no changes are detected in the file, the editing state remains NO for the file and it is not imported into Contenta.
- If there is a new file, a new object is created and populated with the new data. If a new graphic was added, it must exist in the Graphics directory to be imported.
- Files that were deleted during the editing session results in the corresponding Contenta object being deleted.
- The Checkin tool names the objects using the filenames in the checkout directory. The filenames/object names must conform to the Contenta naming standards—for example:
- Names must be less than 50 characters
- Names should not contain the following special characters:
~!@#$%^&*()_+{}|[]\:”;’<>?,/
Troubleshooting tip:
The Web FrameBookCheckin tool cannot find checkout/checkin directories with spaces in the folder name.
See thre SDL Contenta Administration User Guide and/or the SDL Contenta Explorer User Guide for more information about naming standards.