Required?: NO
Authenticated Request?: YES
Request Arguments: Generic Proxy Tool Request Arguments, content_id, course_id, backup_id, type
Sample Implementation: ContentHandlerAction.java ?action=content-imported
Possible Deferred Event: YES
Action on Failure Return: Error message added to import log file; Import continues; event is NOT queued for later delivery.
Action on Communications error: Error message added to import log file; Import continues; Error logged to application log file; Event is queued up to be delivered later (see Deferred Event Delivery).
Action when proxy tool not available: Event queued for later delivery
Action when proxy tool not present on system but locator XML included in backup: Event queued for later delivery.

If specified then this request is called as a simple XML response method. This request is called during course Import and Restore operations to let you link up an appropriate copy of your tool-specific data to be associated with the export/archive file (that you made during the content-exported callback).

The extra arguments are:

• content_id: The new ID of the content item being imported.
• course_id: The course being imported.
• backup_id: A unique identifier for the export/archive file being imported/restored. Use this to link up the data you saved when the user exported/archived the file originally.
• type: exact or shallow. exact means the per-user data for this item can be restored, shallow means that only metadata for your content can be restored, not the per-user data.

To restore per-course data as part of the courseimported handler and is required for the content item, make sure the logic is reflected in this handler. This content can be imported by itself (user chooses to export content areas but not settings and then uses that file to import).

Refer to Content Exchange and Proxy Tools for an outline of how this fits into the bigger contentexchange picture.