When you initially check in new content, the check-in process adds the file to the Server as the newest version in the document hierarchy and places the file under version control. When you check in existing content, the check-in process adds the content as a new version.
To prevent others from editing content a lock may be placed on the content when it is checked out. If the content is locked by an author, the content cannot be checked in by a different author. The author has the option to release the lock.
|
NOTE:
|
The check-in functionality does not support pinning, branching, or merging. In other words, you cannot label (pin) content with a particular version, make a copy of the content (branch), edit the copy, and merge the copy back into the original.
|
Using batch check-in mode, you can check in a folder of content or managed documents via the Editor.
For information on linking to legacy ANCILE Info Pak content from the Server, refer to "Incorporating Info Pak Content" in the companion manual Migration Wizard.
Checking in the Active Content
- Create or open a document or course.
- Select .
- Complete the following fields:
|
Field
|
Description
|
|
Project
|
This field is automatically populated based on the project specified during document creation.
|
|
File Destination
|
Based on the project specified, the File Destination box is populated with the folders and available document binders.
Click on the target folder for this document.
|
|
Lock file for editing
|
To lock the document and prevent editing, select the Lock file for editing checkbox.
|
- Click OK.
|
NOTE:
|
A processing window is displayed. When the check in is complete, a confirmation prompt is displayed.
|
Checking In a Managed Document
In addition to uPerform documents, you can check in a managed document via the Editor using batch check in. Managed documents may include files such as Microsoft PowerPoint presentations, and Microsoft Excel spreadsheets.
|
NOTE:
|
Managed documents are not tracked via the Editor. If you check a managed document into the Server via the Editor a second time, the file is added as a new document.
|
For information on adding or updating a managed document via the Server, refer to "Adding a Managed Document and Updating Properties" in the companion manual Managing Content.
Refer to Checking In Using Batch Mode for complete details on using the Editor to check managed documents into the Server.
Checking In a Single File
- Select .
- Complete the following fields:
|
Field
|
Description
|
|
File name:
|
Click Browse... to locate the folder containing the content to be checked in. From the Files of Type drop-down menu, select a file type.
|
|
Project:
|
The project field displays the project assigned to the file to when it was created. This field cannot be edited.
|
|
File Destination:
|
Expand the document library to specify the destination folder or a document binder.
If you have previously checked in this content, the content will be checked into the original location, regardless of your selection in this field.
|
- Click OK.
|
NOTE:
|
A processing window is displayed. When the check in is complete, a confirmation prompt is displayed.
|
Checking In Using Batch Mode
- Select .
- Complete the following fields:
|
Field
|
Description
|
|
Root directory
|
The default save location is populated in this field.
Click Browse... to specify an alternate folder containing the content to be checked in.
|
|
File Types to Include
|
Use the drop-down list to specify the file types to be checked in from the root directory.
|
|
Managed Document Language
|
Select the language of the managed document for managed documents.
|
|
Project
|
Select the destination project from the drop-down list.
|
|
File Destination
|
Expand the document library to specify the destination folder or document binder.
If you have previously checked in content in the batch collection, the content will be checked into the original location, regardless of your selection in this field.
|
- Click OK.
|
NOTE:
|
A processing window is displayed. When the check in is complete, a confirmation prompt is displayed. Files that were not checked in are noted in the batch check-in log.
|
|
NOTE:
|
During the batch process, new content is added to the Server, and changed content is updated and versioned.
|