Add a new asset
to a scopeWith the CELUM Drive desktop app, you can create, delete, and modify CELUM Content assets or Workroom content online or directly in your local file system. Both online and local changes will be detected by the app and synchronised.
For CELUM Content, restrictions may apply from the server side. Consult the dedicated sub-topic on special cases for CELUM Content for more information.
The affected use cases below are marked accordingly.
Add a new asset
to a scopeCreate assets inside a scope's root folder in your local file system in the following ways:
Drag and drop assets in your scope's
root folder.
Dragging and dropping assets from another synced scope may not change the synced state of the target scope. Should this happen, please consult the section "Moving assets between synced scopes" in our CELUM Drive Knowledge Base.
Create a new asset in a program or via the context menu.
To add an asset to the CELUM Work online repository, consult the CELUM Work online help. Adding assets to CELUM Content is described in the CELUM Content online help topics for Advanced UI or Nova UI.
Creating a folder in your local file system's CELUM location is not supported. If a folder is created, it will be ignored and the assets inside it will not get synchronised. Actions such as renaming and deleting folders will also be ignored.
Synchronise
a new versionAfter updating your asset in your local file system, the scope will be in "Not in sync" state in the CELUM Drive desktop app. When the scope is synchronized, the changed asset will be uploaded to your online repository as a new asset version.
When a new asset version is added in your online repository, the scope will be in "Not in sync" state in the CELUM Drive desktop app. When the scope is synchronized, the new asset version will replace the old version in your local CELUM location.
Revert to a
previous versionIf the current asset version in a synchronised scope is changed to a previous version, the scope will be in "Not in sync" state. When the scope is synchronised, the new current version is reflected in the local file system as well.
You can change the current version either by deleting the newest version or by making a previous version current in the CELUM Content or CELUM Work browser application.
Rename objectsYou can rename the following objects either locally or in the online repository:
Scopes
Renaming restrictions
Only Workroom moderators in CELUM Work or users with a permission to edit collections in CELUM Content can edit the name of a scope. Renaming a scope locally as a contributor in CELUM Work or without the edit permission in CELUM Content will cause a "Renaming failed" error and the scope will have a "Not in sync" status. Visit the section "Resolve scope 'Renaming failed' error" in our CELUM Drive Knowledge Base for the solution.
Assets
If you rename a scope or an asset in either the local file system (your CELUM location) or in the online repository, the same action will also be reflected in all other connected people's file systems if they are subscribed to the same scope.
If an asset is simultaneously being renamed locally and online, a renaming conflict will occur. You can solve this conflict in the "Conflicts" tab.
If the chosen object name in the repository contains unsupported characters, these will be replaced with a safe character in the CELUM location. This affects, for example, the characters ", /, \, ?, *, <, >, or | on Windows®, as well as ~ on macOS®.
Different file path length restrictions on Windows and macOS can lead to problems with long asset names. On Windows®, the entire path of an asset (folder path, asset name and file extension) can have a maximum of 255 characters. On macOS®, the entire file path can exceed 255 characters. The file name (with extension) alone has a limit of 255 characters.
Delete objectsIf you delete an asset or a scope in the online repository, the action will also be reflected in all other people's file systems if they are subscribed to the same scope.
Deleting a scope locally is not possible. When deleted, the scope will be re-synced again. Depending on your settings, deleting an asset locally will result in a tracking conflict, or will be moved to the trash bin of the repository.