The preserve item authorship/ownership feature allows for files being copied/synced/or migrated to maintain their original author/owner information. In order to preserve authorship, both the source platform connector and the destination platform connector must support this feature (see: Platform Comparison).
While DryvIQ will automatically attempt to map users based on various rules, such as name and actual ID, it is also possible to map specific users from one platform to another. This is useful when a user no longer exists or when a users name, email, or other identifiable information is different from one platform to the next.
The Preserve Destination root folder authorship option allows you to preserve authorship for the root folder. Note that authorship will only be preserved if DryvIQ creates the root folder on the destination as part of the transfer. If the root folder already exists on the destination, the authorship from the source will not be preserved on the destination. Instead, authorship on the destination will be whoever created the root folder on the destination.
Author/Owner Preservation Tracking
DryvIQ tracks associations between items and user mappings, similar to permission tracking. Users who created or modified the item or its versions (when applicable) will be displayed on the User mapping tab of the job page. For author/owner preservation tracking to work, the job audit level must be set to at least "Info" (the default level for the DryvIQ user-interface). See Logs | Installer, Application, and Job for more information on log levels.
Configuration Using the REST API
Author/Owner Preservation options include:
The parameters to note in this example are preserve_owners, permissions, and account_map.