Link a project to a Helix Core Server classic depot

Note

  • You must be a Helix DAM admin or the project admin to link a project to a classic depot.

  • User permissions for assets in linked classic depots are managed by Helix Core Server. To set permissions for project members, see Authorizing access in Helix Core Server Administrator Guide.

Helix DAM can manage assets held in your existing Helix Core Server classic depots by linking them to projects in Helix DAM. Classic depot linking can be used for projects created with auto depot creation disabled. See Create a project. For information on classic depots, also known as local depots, see Local depots in the Helix Core Server Administrator Guide .

When you link a project to a classic depot, it is displayed in the Helix DAM project as a repository. The branches are displayed in the repository as collections. Folders in collections contain the assets and may contain subfolders.

  1. Open the project to link a classic depot to.

  2. Below your avatar, click Link to depots and select Link to classic depot.

  3. In the Link to classic depot dialog box, enter a Helix DAM repository display name for the Helix DAM repository. The name cannot contain any spaces or special characters, but it can contain the minus (-) and underscore (_) characters.

  4. Enter a Branch display name for the Helix DAM collection. The name cannot contain any spaces or special characters, but it can contain the minus (-) and underscore (_) characters.

  5. Enter the File path for the branch to link to.

    • The file path must start with // followed by an existing depot name.

    • Wildcards should not be used; the only exception is that the branch file path can end with the Helix Core Server wildcard ...

    • Branch file paths are case sensitive.

    • If using multiple file paths, add each path on a separate line.

    • Branch paths are processed in order, starting with the first file path in the list.

    Example:

      //depot/game1/assets/...

      //depot/game1/test/ResultSummary.html

      The first path includes all of the directories and files under //depot/game1/assets/... in the branch.

      The second path includes the ResultSummary.html file from the //depot/game1/test/ directory.

  6. Click Create.

    The repository is added to the project and up to four collections are displayed in the new repository. To see all collections in the repository, click the repository to expand it.

Where to go next