Project Stor 攀㌀⸀㜀⸀㈀唀猀攀爠ᤀ猀 േuide - Tiger Technology · 2020. 6. 27. · 28 Feb. 2017 Downloading the Projects List as a .csv File functionality added. 65

February 28, 2017

User’s Guide

© Copyright 2008 - 2017 Tiger Technology. All rights reserved.

This publication, or parts thereof, may not be reproduced in any form, by any method, for any purpose.

TIGER TECHNOLOGY MAKES NO WARRANTY, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES, OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, REGARDING THESE MATERIALS AND MAKES SUCH MATERIALS AVAILABLE SOLELY ON AN “AS-IS” BASIS.

IN NO EVENT SHALL TIGER TECHNOLOGY BE LIABLE TO ANYONE FOR SPECIAL, COLLATERAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH OR ARISING OUT OF PURCHASE OR USE OF THESE MATERIALS. THE SOLE AND EXCLUSIVE LIABILITY TO TIGER TECHNOLOGY, REGARDLESS OF THE FORM OF ACTION, SHALL NOT EXCEED THE PURCHASE PRICE OF THE MATERIALS DESCRIBED HEREIN.

Tiger Technology reserves the right to revise and improve its products as it sees fit. This publication describes the state of this product at the time of its publication, and may not reflect the product at all times in the future.

THIRD-PARTY TRADEMARKS

All other brand names, product names, or trademarks belong to their respective holders.

Manual Revision and Control

Title: Project Store User’s GuideSoftware version: Project Store 3.7.2Publication Number:Date: February 28, 2017

Revision Record

Date Description Page Version

01 Oct. 2014 Initial Draft 3.5.1

27 Mar. 2015 To enable Project Store support on more than one volume, these volumes no longer need to be part of a smart storage pool.

12 3.6

27 Mar. 2015 Project Store and Smart Storage Pooling section added. 12 3.6

27 Mar. 2015 When importing a project into the depot, you can select on which volume to import it.

83 3.6

13 Jul. 2015 Hiding Project Store Volumes section added. 14 3.6.2

01 Oct. 2015 Project quotas setting added. 46 3.7

01 Oct. 2015 Creating projects as administrator functionality added. 31 3.7

01 Oct. 2015 Added support for Tiger Store storage server running Windows® 10.

6 3.7

04 Nov. 2015 Project quotas cannot be enabled if Project Store support is enabled on a volume pool.

16 3.7.1

20 Nov. 2015 Rescanning a Project section added. 64 3.7.1

28 Feb. 2017 Preserving projects last mount state per user option added. 17 3.7.2

28 Feb. 2017 Creating and managing groups of Project Store users option added. 20, 22, 26, 29

3.7.2

28 Feb. 2017 Replication status of projects available. 31 3.7.2

28 Feb. 2017 Deleting multiple projects simultaneously functionality added. 37 3.7.2

28 Feb. 2017 Downloading the Projects List as a .csv File functionality added. 65 3.7.2

28 Feb. 2017 When project quota setting is enabled, users cannot import projects into the projects depot.

83 3.7.2

Revision Record

Date Description Page Version

1

Table of Contents

1 Installing and Uninstalling Project Store 3Installing and Uninstalling Project Store . . . . . . . . . . . . . . . . . 5

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 6Installing Project Store . . . . . . . . . . . . . . . . . . . . . . . . . 6Activating Project Store . . . . . . . . . . . . . . . . . . . . . . . . . 7Upgrading Project Store . . . . . . . . . . . . . . . . . . . . . . . . . 7Uninstalling Project Store . . . . . . . . . . . . . . . . . . . . . . . . 8

2 Administrating Project Store 9Accessing the Administrative Interface . . . . . . . . . . . . . . . . . . 10Initial Setup of Project Store . . . . . . . . . . . . . . . . . . . . . . . . . 11

Enabling and Disabling Support for Project Store . . . . . . . 12Hiding Project Store Volumes . . . . . . . . . . . . . . . . . . . . . 14Setting Up the Deployment Environment . . . . . . . . . . . . . 15Enabling Project Quotas . . . . . . . . . . . . . . . . . . . . . . . . . 16Preserving Projects Last Mount State . . . . . . . . . . . . . . . . 17Enabling and Disabling Security . . . . . . . . . . . . . . . . . . . 18Managing Project Store User Accounts and Groups . . . . . . 19

Managing Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Create a New Project as Administrator . . . . . . . . . . . . . . . 31Renaming a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Deleting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Editing the Project Description . . . . . . . . . . . . . . . . . . . . 38Editing the Project Keywords . . . . . . . . . . . . . . . . . . . . . 39Setting Project Permissions . . . . . . . . . . . . . . . . . . . . . . 42Setting Preferred Mount Point of a Project . . . . . . . . . . . . 45Setting/Changing the Project Quota . . . . . . . . . . . . . . . . . 46Exporting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Moving a Project Between Volumes . . . . . . . . . . . . . . . . . 50Lock a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Force Closing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Optimizing the Project Store Workflow . . . . . . . . . . . . . . . . . . 53Managing Proxies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Table of Contents

2

Setting a Project as Template . . . . . . . . . . . . . . . . . . . . . 60Resetting the Projects’ Database . . . . . . . . . . . . . . . . . . . 63Rescanning a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Downloading the Projects List as a .csv File . . . . . . . . . . . 65

Viewing the Activity Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

3 Working with Project Store 69Accessing the User Interface of Project Store . . . . . . . . . . 70

The User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Resetting the Password of Your Project Store Account . . . . . . . 74Searching The Projects Depot . . . . . . . . . . . . . . . . . . . . . . . . 74Working with Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Create a New Empty Project . . . . . . . . . . . . . . . . . . . . . . 78Create a New Project from Template . . . . . . . . . . . . . . . . 80Import an Existing Project into Project Store . . . . . . . . . . 83Exporting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Mount a Project for Viewing . . . . . . . . . . . . . . . . . . . . . . 86Mount a Project for Editing . . . . . . . . . . . . . . . . . . . . . . . 87Lock a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Close a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Delete a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Preview a Project without Mounting It . . . . . . . . . . . . . . . 91

Editing Project Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Rename a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Editing the Project Description . . . . . . . . . . . . . . . . . . . . 97Editing the Project Keywords . . . . . . . . . . . . . . . . . . . . . 99Editing the Project Type . . . . . . . . . . . . . . . . . . . . . . . . . 100Setting a Project as Template . . . . . . . . . . . . . . . . . . . . . 102Setting Project Permissions . . . . . . . . . . . . . . . . . . . . . . 104Setting Preferred Mount Point of a Project . . . . . . . . . . . . 107Moving a Project Between Volumes . . . . . . . . . . . . . . . . . 109

Installing and Uninstalling Project Store

System Requirements . . . . . . . . . . . . . . . . . . . . 6

Installing Project Store . . . . . . . . . . . . . . . . . . . 6

Activating Project Store . . . . . . . . . . . . . . . . . . . 7

Upgrading Project Store . . . . . . . . . . . . . . . . . . . 7

Installing and Uninstalling Project Store . . . . . . . . 5


4

Designed specifically for the Tiger Series product line, Project Store is the ultimate solution for project collaboration in shared storage environment. The basic purpose that Project Store serves is to allow creating and mounting shared projects each as a separate local drive on Tiger Client computers. A client can mount any number of project folders exclusively, with Read and Write permissions or for previewing only. Based on this functionality Project Store allows you to build up your workflow depending on the environment in which you deploy it and your needs.

You can benefit from the product’s basic functionality (create, mount, delete, rename projects) using the starter edition of the software, Project Store SE, which doesn’t require activation. The licensed version, Project Store adds up features, which enhance your workflow with project permissions (of domain or Project Store users), automatic parsing of projects data and generation of proxy media each time a project mounted for editing is dismounted, faster browsing of projects without having to mount them, setting projects as templates and creating projects based on templates.

You can compare the features available in Project Store SE and Project Store here:

Project Store SE Project Store

create an empty project

create a project from template -

import an existing project folder

mount a project with Read & Write permissions

mount a project for previewing only

mount a project exclusively

mount a project by multiple users simultaneously -

lock a project -

rename a project

delete a project

set a project as template -

emulate the project drive’s file system to Avid FS

close a project

force close a project

export a project outside the projects depot

move a project from one volume to another


5

All administration of Project Store is performed from one central location (the web interface) and changes are immediately detected by all connected computers.

Note: Changes of the shared storage configuration (such as shared/unshared volumes, enabling/disabling of smart storage pooling, etc.) take up to a minute to get detected in the web interface of Project Store.

With Project Store, non-Tiger Client computers are not left out of the workflow – while they cannot actually work with the projects in the depot, by accessing Project Store’s web interface from a remote computer (a computer that cannot mount the shared storage volume, but is on the same network as the Tiger Clients) you can preview data in any project folder that is accessible to your account.

Installing and Uninstalling Project StoreVersion 2.5.1 and later of all Tiger Series appliances comes with Project Store pre-installed. You should manually install Project Store on the metadata controller of your Tiger Store network. There’s no need to install Project Store client software on Tiger Client computers. As long as Project Store is installed on the storage server, each Tiger Client can access and work with projects in the projects depot. In order to benefit from Project Store’s features, it must be activated on the metadata controller computer on your Tiger Series network.

move a project between volumes in a pool*

set project quota -

add project description and keyword

edit the project description and keywords -

apply project permissions -

set preferred mount point of a project

automatic parsing of projects’ data -

automatic generation of proxy media -

browsing projects’ contents without mounting them

-

preserve mount state of projects on client computers

-

download projects’ list as a .csv file -

Project Store SE Project Store


6

In case you’re already running a previous version of Project Store, you have to upgrade to this new version, following the steps described in “Upgrading Project Store” on page 7.

System RequirementsCurrently, you can work with Project Store on Windows, Mac OS X and Linux computers that run the Tiger Client software and are connected to a Tiger Series metadata controller running at least version 2.5.1.

Project Store 3.5.1 and later comes pre-installed on all Tiger Series appliances. To use Project Store on your Tiger Store network, you should install it on the metadata controller computer. While Project Store can normally work on a computer meeting the minimum system requirements of Tiger Store, to guarantee best performance with Project Store, it is advisable to install it on a computer that meets these minimum system requirements:

• PC with 2.5-GHz 64-bit (x64) processor.

• 64-bit Microsoft Windows® 7/Server 2008 R2/Windows® 8/Server 2012/Server 2012 R2/Windows® 10.

Important: To be able to benefit from the project quota feature, the Tiger Store computer must run a server OS - Microsoft Windows® Server 2008 R2/Server 2012/Server 2012 R2.

• 8Gb of physical RAM at least.

• 200MB of available hard-disk space for installation.

• TCP port 8480 must not be blocked by a firewall if any.

Installing Project StoreProject Store comes pre-installed on each Tiger Series appliance. To use Project Store on your Tiger Store network, you should install it on the metadata controller, supervising the volumes, on which the projects depot will be stored.

Note: No client installation is required. As long as a computer runs the Tiger Client software, it can work with Project Store.

To install Project Store on the Tiger Store metadata controller:1. On the selected computer, log on using an account with administrative privileges.

2. Browse for and double-click the Project Store installation file and then click Next.

3. Accept the terms of the software license agreement and click Next.

4. Click Install.

5. When the installation finishes, click Close.


7

6. Restart the computer.

Activating Project StoreIn order to unlock functionality available in Project Store, you need to activate the product on your metadata controller – the Tiger Series appliance or the Tiger Store computer. For activation Project Store makes use of a software-protection dongle. The dongle is already plugged on your Tiger Series appliance. On a Tiger Store metadata controller, you must plug the dongle yourself. If the correct activation file is not uploaded on the dongle, Project Store operates with limited functionality (see features comparison table for more details). For detailed activation instructions, refer to the accompanying software dongle documentation.

Note: There’s no need for activation of Project Store on client computers.

Upgrading Project StoreYou can upgrade any previous version of Project Store to a newer version. When you upgrade from version 3.5.1 there’s no need to uninstall the previous version of the product - simply run the new installation on the Tiger Store computer or upload the new installation as a firmware update on the appliance. All projects, users and settings are kept, except the settings for proxies generation and project permissions (these are reset to their defaults). After the upgrade data generated by the parsers (proxy media, project structure, application type, size, number of files in the project folder, etc.) is lost and you need to rescan your projects to re-generate it.

To upgrade from Project Store 2.x or Project Store 3.5, you should disable support for Project Store 2.x/3.5, uninstall any previous version of the software from the metadata controller and install the new one. As versions 3.5.1 and later don’t require any client software, to upgrade your Tiger Client computers, you should simply uninstall any previous version of Project Store.

Note: Version 2.5.1 and later of all Tiger Series appliances comes with Project Store pre-installed. To upgrade their Project Store version, contact Tiger Technology support for assistance.

For uninstallation steps, refer to the Project Store 2.0 Help:http://www.tiger-technology.com/projectstore_help

While all projects created with Project Store 2.0/3.5 are automatically detected by Project Store 3.5.1 and later, they need additional set up in order to guarantee the complete compatibility between the two versions. For more details, see “Setting Up Legacy Projects” on page 8.

To upload the new Project Store installation as a firmware update:1. Access the web interface of the appliance and go to System | Maintenance.

2. In the Maintenance page, click Enter Maintenance Mode and then confirm that you want to enter Maintenance mode.


8

Important: All connected client computers will be automatically disconnected from the shared volumes and any file operation going on at the moment will be canceled.

3. In Firmware Update, click Browse/Choose file and then browse for and select the file containing the Project Store installation to upload.

4. Click Continue to confirm that you want to perform the update.

The system automatically restarts after the Project Store update finishes and all clients can connect to the volumes.

Setting Up Legacy ProjectsAfter upgrading to Project Store 3.5.1 or later you can still use all your legacy projects (projects created with Project Store 2.x or Project Store 3.5).

Projects created with Project Store 2.x are without owner after you upgrade to Project Store 3.5.1 or later. It is advisable to set the owner of each legacy project, following the steps in “Setting Project Permissions” on page 42.

Uninstalling Project StoreYou can uninstall Project Store from your Tiger Series appliance or the metadata controller of your Tiger Store network at any time. Once you uninstall Project Store, the projects depot folder and all its contents on the shared storage volume/the volume pool becomes visible to anyone having access to it.

To uninstall Project Store from a Tiger Series appliance, you should request assistance from Tiger Technology support. You can manually uninstall Project Store from your Tiger Store metadata controller.

Note: Even if you uninstall Project Store from a Tiger Series appliance, the domain user accounts in the “projectStore Admins” and “projectStore Users” groups are kept in case you decide to re-install Project Store again and re-use them.

To uninstall Project Store from Tiger Store:1. In Control Panel, double-click Programs and Features.

2. Right-click Project Store and select Uninstall.

3. When prompted to confirm that you want to remove Project Store from the computer, click Yes.

The uninstallation of Project Store warns you that you will have to reboot the computer to complete the uninstallation.

4. Click OK.

5. When prompted, restart the computer.

Administrating Project Store

Accessing the Administrative Interface . . . . . . . 10

Initial Setup of Project Store . . . . . . . . . . . . . . 11

Managing Projects . . . . . . . . . . . . . . . . . . . . . . 29

Optimizing the Project Store Workflow . . . . . . . . 53


10

You can work with and manage Project Store through its web interface. To manage Project Store settings and control project folder settings, you should access the administrative interface of Project Store. It serves three goals:

Initial setup — allows you to set Project Store up in order to allow creating of project folders and collaboration across projects from client computers. See “Initial Setup of Project Store” on page 11.

Optimization mechanisms — allow you to configure Project Store settings that enhance user experience with the product:

• proxies generation – lets users preview project contents in the Project Store browser, without having to mount the project. See “Managing Proxies” on page 53.

• creating of project templates – set certain project folders as templates in order to facilitate users in reproducing the folder structure and copying data when creating a new project. See “Setting a Project as Template” on page 60.

• resetting the projects database – clean all projects information (project size, application type, number of files, users, etc.) in case the database containing it becomes corrupted and fails to display results correctly. See “Resetting the Projects’ Database” on page 63.

Projects control — allows you to rename, delete, change permissions, clear proxies, etc. of any given project in the projects depot (see “Managing Projects” on page 29) and download the list of all projects and their details as a .csv file (see “Downloading the Projects List as a .csv File” on page 65).

All administrators of Project Store can also view a log of all activity related to Project Store settings, users and projects. For more information, see “Viewing the Activity Log” on page 66.

Accessing the Administrative InterfaceTo access the Administrative interface, you have to log on to Project Store with an administrative account.

When accessing Project Store for the first time, you can use for authentication the following automatically created administrative account:

User name: psadmin

Password: psadmin

If you deploy Project Store in workgroup environment, you can log on to the Administrative interface with an internally created Project Store administrative account. You can create as many administrative accounts as you want, following the steps described in “Managing Project Store User Accounts and Groups” on page 19.

Initial Setup of Project Store

11

If you deploy Project Store in an Active Directory domain, you can access the administrative interface with an account, which is a member of the “projectStore Admins” group on the domain controller.

Note: If such group doesn’t exist, you have to manually create it. If you want to use the account(s) in a different group on the domain controller, contact Tiger Technology support for assistance.

To access the administrative interface of Project Store:1. In the address bar of a web browser, type this:

http://[IP address or name of a computer with Project Store installed]:8480

Important: To access the administrative interface using the computer’s name instead of IP address, a DNS server on the network must resolve the IP address to its domain name.

2. Enter an administrator’s user name and password, then click Login.

Tip: To log out Project Store, in the top band, click Log out.

Initial Setup of Project StoreThe initial setup allows you to get started with Project Store without having to configure any additional settings. It includes the following:

• enabling Project Store support on the selected volume(s).

• selecting whether to hide a volume on which Project Store support is enabled on all Tiger Client computers.

• selecting whether to enable project quotas.

• select whether Project Store should preserve the projects last mount state on client computers.


12

• set Project Store up depending on the environment in which the volume(s) will be accessed – without security, workgroup environment or domain environment.

Enabling and Disabling Support for Project StoreFor Project Store to create the projects depot on a volume and allow users to create project folders and mount them for viewing or editing you should first enable Project Store support on one or more shared volumes or a volume pool.

You can enable/disable support for Project Store at any time. When you disable support for Project Store the contents of each projects depot automatically becomes visible to any connected computer in the “projectstore” folder in the root of each volume and access to projects in this folder depends only on the security applied to the volume itself.

Important: If a folder named “projectstore” already exist in the root of the volume, you cannot disable Project Store support until you rename that folder.

Enabling support for Project Store anew automatically restores the last applied Project Store settings.

Project Store and Smart Storage PoolingWhen smart storage pooling is enabled on your Tiger Series metadata controller, you can enable Project Store support on the volume pool instead of the individual volumes. In this case a separate projects depot is created on each of the volumes in the pool. When creating a new project, you can choose on which volume in the pool to store it. When you want to import an ambiguous folder (a folder with the same name existing in the same location on two or more volumes in the pool), it contains the merged contents of all ambiguous folders with the same name, but has the attributes of the ambiguous folder that is on the volume first detected by the metadata controller service at the time you perform the import operation. The same rule applies for ambiguous files in ambiguous folders that are being imported - Project Store will import just the file in the ambiguous folder first detected by the metadata controller service.

If you have enabled Project Store support on a volume pool, which is later disbanded on the metadata controller, Project Store automatically enables support on each of the volumes that had participated in the pool. Vice versa, when Project Store support is enabled on multiple volumes, which are later added to a smart storage pool on the metadata controller, Project Store automatically enables the support on all volumes in the volume pool, even if it has not been enabled on some of them before. In this case ambiguity can occur as it is possible project folders with identical names to exist in the project depots of two or more volumes that now are part of a pool. To avoid problems with ambiguous projects, it is advisable to check the list of all projects on all volumes and rename one or the other ambiguous project before enabling smart storage pooling.

When a volume, on which Project Store support had been once enabled, but was then disabled (all projects became visible in the "projectstore" folder on the root of the volume) is added to a smart storage pool that contains a volume with enabled Project Store support, support for Project Store is automatically enabled


13

on all volumes in the pool and the projects from the "projectstore" folder on the root of that volume are accessible from the projects depot.

To enable support for Project Store:1. In the Administrative interface, click General Settings.

2. In Enable/Disable Project Store, select the Enable check box of each volume or the volume pool on which to enable support for Project Store.

Project Store support is enabled for the volume(s)/volume pool.

To disable support for Project Store:1. In the Administrative interface, click General Settings.

2. In Enable/Disable Project Store, clear the Enable check box of each volume/the volume pool, to disable Project Store support on it.

Important: If a folder named “projectstore” already exists in the root of the volume on which you disable support, Project Store warns you that you need to rename this folder, before you can proceed.

Project Store support is disabled for the volume(s)/volume pool and the contents of the projects depot is visible to any user accessing the volume(s) in the “projectstore” folder.


14

Hiding Project Store VolumesTo ensure that a volume is used solely for storing Project Store data, you can hide it on all Tiger Client computers. That way, even when a Tiger Client connects to the storage server, no hidden volume will be mounted on the computer and users will be able to mount just project drives through the Project Store web interface. You can choose to hide just a selected volume, on which Project Store support is enabled and allow other Project Store volumes to be mounted on Tiger Clients. When Project Store support is enabled on a volume pool and you select to hide the pool, no volume part of the pool will be mounted on Tiger Client computers. You can hide/unhide a Project Store volume at any time.

Note: You cannot hide a volume, on which Project Store support is not enabled.

To hide/unhide a Project Store volume:1. In the Administrative interface, click General Settings.

2. In Enable/Disable Project Store, do one of the following:

• Select the Hide Volume check box of each volume/the volume pool, to hide it on Tiger Clients.

• Clear the Hide Volume check box of each volume/the volume pool, to let Tiger Clients mount it when they connect to the storage server.


15

Setting Up the Deployment EnvironmentRegardless of the environment, in which the Project Store volumes are accessible, you can deploy Project Store without any security restrictions for users. This means that as long as a volume is accessible to any given computer, users can create project folders on it and there are no restrictions regarding who can view and mount for editing a project folder as long as its status is “Available”.

You can switch your Project Store setup to a deployment with no security at any time. See “Enabling and Disabling Security” on page 18.

Active Directory Domain EnvironmentTo be able to use Project Store in an Active Directory domain, you should create two groups of users on your domain controller:

projectStore Admins — all users in this group will be able to access the administrative interface of Project Store and act as Project Store administrators;

projectStore Users — all users in this group will be able to work with Project Store (access the projects depot and work with projects) depending on the access permissions assigned to them;

Important: If a domain user is a member of both "projectStore Admins" and "projectStore Users" groups, that user gains access to the Administrative interface only and cannot work with projects.

Project Store automatically detects if your Tiger Series metadata controller is part of an Active Directory domain and authenticates accesses to the project folders using the permissions set for users of the ‘projectSore Users’ group on the domain controller. If security is not disabled in Project Store, in the web interface you can set the access permissions (owner, edit, view) of each project folder. For more information, refer to “Setting Project Permissions” on page 42.

Workgroup EnvironmentWhen your Tiger Series metadata controller is not in an Active Directory domain, you can still benefit from security by deploying Project Store in workgroup environment, in which accesses depend on the permissions assigned to internally created Project Store user accounts. Project Store user accounts are stored in a database common for all client computers. Only users that log on with a valid Project Store user account can access the projects depot and create and work with project folders. Additionally, if security is not disabled in Project Store, in the web interface you can set the access permissions (owner, edit, view) of each project folder. For more information, refer to “Setting Project Permissions” on page 42.

For more information about creating the Project Store users database, refer to “Managing Project Store User Accounts and Groups” on page 19.


16

Enabling Project QuotasImportant: You can benefit from the project quotas feature only when Project Store is installed on a Tiger Series appliance or a Tiger Store storage server running server OS.

The project quotas setting allows you to specify the maximum size of a project on the shared volume. The quota you specify does not reserve space on the volume for the project, but serves just as a limit to the size of the project. Thus, whenever a user attempts to write new files to a project, which has reached its quota, Project Store displays a message that there is not enough free space, although the volume, on which the projects depot is, may have more free space. You can specify a quota that is bigger than both the free space on the volume and its overall size, which will indicate that there’s no limit for the size of the specific project. Similarly, a project without quota setting can take as much space on the volume as possible. Project Store doesn’t calculate the sum of all quotas you specify - should the volume run out of free space, even if a project hasn’t reached its quota limit, users will not be able to write new data to it.

To allow for greater control of project quotas, once you enable this option only a Project Store administrator can create new projects and assign quotas to them and Project Store users can only work with already created projects and manage their other settings. For more information about creating new projects as a Project Store administrator and managing project quotas, refer to “Create a New Project as Administrator” on page 31. Additionally, once project quotas are enabled, users cannot import projects into the projects depot.

Project quotas are supported only if Project Store support is enabled on individual volumes. When Project Store support is enabled on a volume pool, you cannot enable project quotas. Similarly, as long as project quotas are enabled in Project Store, you cannot enable smart storage pooling on your storage server. You can enable and disable project quotas at any time. If you enable project quotas after there are already projects created or imported into the depot, it is advisable to set a quota for each of them. For more information, refer to “Setting/Changing the Project Quota” on page 46. Keep in mind that once you disable quotas the project quota setting is lost and you will have to manually assign a quota to each project, should you decide to enable them again.

To enable/disable project quotas:1. In the administrative interface of Project Store, click General Settings.

2. In Enable/Disable Project Store do one of the following:


17

• Select the “Enable project quota” check box, to enable project quotas.

Important: You cannot enable project quotas if Project Store support is enabled on a volume pool.

• Clear the “Enable project quota” check box, to disable project quotas.

3. Click Save.

Preserving Projects Last Mount StateBy default, each time you want to work with a project as a user, you must access the user interface of Project Store and manually mount each selected project. To facilitate users workflow, an administrator can set Project Store to preserve the last mount state of projects for all users. This means that once a user logs in to the user interface, Project Store attempts to automatically mount all projects the user has mounted before logging out or restarting/shutting down the computer. Thus, when the user logs in to the user interface, Project Store attempts to mount the projects with the same permissions (Read Only, Read & Write or Exclusively) as long as they are available. A project is removed from a user’s list of last mounted projects only if the user explicitly dismounts it by closing it in the user interface. A project can be in two or more users’s last mounted projects list. In this case Project Store mounts it for the user that logs in the user interface first.


18

To enable/disable preserving projects last mount state:1. In the administrative interface of Project Store, click General Settings.

2. In Enable/Disable Project Store, do one of the following:

• Select the “Preserve last mount state” check box, to set Project Store to attempt to automatically mount the last mounted projects.

• Clear the “Preserve last mount state” check box, to let users manually mount the projects they want.

3. Click Save.

Enabling and Disabling SecurityRegardless of the environment in which you deploy Project Store, you can select whether to use permissions (owner, edit, view) for access to the project folders or not. If security is disabled, the access to project folders depends only on the current status of the project – Available (you can mount the project for editing or viewing) or In Use (you can mount the project for viewing only).

When security is enabled in domain environment, you must specify the access permissions for each project folder of domain user accounts. When security is enabled in workgroup environment, you must specify the access permissions for each project folder of internal Project Store user accounts.


19

To enable/disable security:1. In the administrative interface of Project Store, click General Settings.

2. In Enable/Disable Project Store do one of the following:

• Select the “Disable project permissions” check box, to disable permissions authentication.

• Clear the “Disable project permissions” check box, to enable permissions authentication for domain or Project Store user accounts.

3. Click Save.

Managing Project Store User Accounts and GroupsWhen Project Store is deployed in an Active Directory domain, the user accounts management is performed the way you would manage domain users – members of the “projectStore Admins” group on the domain controller have access to the Administrative interface of Project Store, while members of the “projectStore Users” group can access the Users interface. The only difference is that you specify the access permissions of domain users to project folders through the Project Store interface (see “Setting Project Permissions” on page 42).

Note: If you want to use the user accounts in a different group on the domain controller, contact Tiger Technology support for assistance.


20

When you deploy Project Store in workgroup environment, to enable access to the User interface and also to benefit from project permissions, you need to create and manage an internal database with user accounts. Each user account is defined by a user name, password and account type - Administrator (the user can access the Administrative interface and manage Project Store settings) or User (the user can access the User interface and work with projects).

To facilitate you in assigning project permissions, Project Store also allows you to unite users into groups and instead of specifying the permissions of each user for a given project, assign permissions to the whole group. You can also specify that a given group is a sub-group of another group. The users in a sub-group automatically inherit the permissions set for the group, unless different permissions are explicitly assigned to the sub-group.

You can modify both user accounts and groups after you create them. You can change the following parameters of a user account - password, type (User or Administrator) and groups the account is member of. You can change the following parameters of a user group - type (Users or Administrators), members (add or delete users), groups it is a sub-group of.

Note: You cannot rename Project Store users or groups. To change the name of a user or group, you have to delete it and then re-create it again with the new name.

As a user account can be a member of both a group of Administrators and a group of Users, Project Store uses the following rule to determine whether the user should have access to the Administrative interface or the User interface - a user gains access to the User interface only if the account type is set as User and it is not a member of any group or sub-group of Administrators. In all other cases the user gains access to the Administrative interface only. Should you decide to change the type of an account from Administrator to User, Project Store automatically removes the user account from all groups of Administrators that it has been part of.


21

To create a Project Store user:1. In the Administrative interface, click User Management.

2. Click Create User.

3. In the Create User dialog, do the following:


22

• Enter the user name and password in the corresponding fields.

• In Type, select User or Administrator.

• In Group, type in the name of an existing Project Store group, to which to add the newly created user account, then click Add.

Tip: You can start typing the name of the group and Project Store will automatically suggest existing groups containing the symbols you have typed.

4. Click Create.

To create a Project Store user group:1. In the Administrative interface, click User Management.

2. Click Create Group.


23

3. In the Create Group dialog, do the following:

• In Group name, enter the name of the group.

• In Type, select whether this will be a group of Users or Administrators.

• In Group, type in the name of an existing Project Store group, to make the newly created group its sub-group, then click Add.


• In Member name, type the name of an existing Project Store user to add it as a member of the group and then click Add.

Important: Keep in mind that if you add a Project Store user to a group of Administrators, that user will have access to the Administrative interface only, even if the account has been created as User or is part of other groups of Users.

Tip: You can start typing the name of the user and Project Store will automatically suggest existing users containing the symbols you have typed.


24

4. Click Create.

To modify a Project Store user account:1. In the administrative interface, click User Management.

2. In the list with Project Store users, find the user account whose information you want to change and click Modify.

Tip: You can sort each column of the list in ascending/descending order to more easily find a user.


25

3. In the Update User dialog, do one of the following:

• To change the password of the user, enter the new password in the corresponding fields.

• To change the type of the user, select User or Administrator in the Type drop-down box.

Important: If you change the type to User, but that account is member of Administrators group(s), Project Store automatically will remove the account from all groups of Administrators.

• To add the user to a group, in Group type the name of the group and then click Add.


• To remove the user from a group, click the Close button next to the group name in the list.

4. Click Update to save the changes.


26

To modify a Project Store user group:1. In the administrative interface, click User Management.

2. In the list with Project Store users and groups, find the group, whose settings you want to change and click Modify.

Tip: You can sort each column of the list in ascending/descending order to more easily find a group.


27

3. In the Update Group dialog, do one of the following:

• To change the type of the group, select User or Administrator in the Type drop-down box.

• To make the group a sub-group of another group, in Group type the name of the other group and click Add.

Tip: You can start typing the name of the group and Project Store will automatically suggest existing groups containing the symbols you have typed in their name.

Important: Be careful not to create circular dependency by setting the group as a sub-group of a group that is already a sub-group of the currently modified group.

• To remove the group from the list of sub-groups, click the Close button next to a group name in the “Member of” list.

• To add a user to the group, in “Member name” type the name of the user and then click Add.

Tip: You can start typing the name of the user and Project Store will automatically suggest existing users containing the symbols you have typed in their name.

• To remove a Project Store user from the members of the group, click the Close button next to the group name in the list.


28

4. Click Update to save the changes.

To delete a Project Store user:1. In the Administrative interface, click User Management.

2. In the list of Project Store users and groups, click Remove next to the user account you want to delete.

Tip: You can sort each column of the list in ascending/descending order to more easily find a user/group.

Important: You cannot delete a Project Store administrator if you are currently logged on with the same account or if there isn’t another Project Store user assigned the role of an administrator.

3. Confirm that you want to delete the account, when prompted.

The deleted user no longer has access to the projects depot and to project folders even if that user is the owner of these projects. It is advisable to assign another user as owner of the deleted user’s projects.

Managing Projects

29

To delete a Project Store user group:1. In the Administrative interface, click User Management.

2. In the list with Project Store users and groups, click Remove next to the group you want to delete.

Tip: You can sort the columns of the list in ascending/descending order to more easily find a user/group.

3. Confirm that you want to delete the account, when prompted.

The members of the deleted group no longer have access to projects, for which permissions have been specified for the delete group and not for each individual user.

Managing ProjectsWhile administrators of Project Store cannot work with projects, in the Project Management page of the Administrative interface they have access to all project folders in each projects depot and can manage them in the following ways:

Rename projects — change the name of the project folder, which automatically changes the name of the project drive, which mounts on client computers. See “Renaming a Project” on page 36.

Delete a project — delete the project folder and its contents from the projects depot. See “Deleting a Project” on page 37.


30

Change the ownership and permissions of a project — while the owner of a project can also change its permissions (select who can edit and view the project), only a Project Store administrator can change the owner of a project folder. See “Setting Project Permissions” on page 42.

Edit the project description — change the description of a project, which helps discerning it from other projects and is also used by the Project Store’s search engine when displaying the results of your search. See “Editing the Project Description” on page 38.

Edit the project keywords — delete or add new keywords to a project; these are used by Project Store’s search engine when displaying the results of your search. See “Editing the Project Keywords” on page 39.

Set preferred project mount point — set a universal mount point of a project on all Windows Tiger Clients - a drive letter or a folder in the C:\Volumes directory. See “Setting Preferred Mount Point of a Project” on page 45.

Set/change the project quota — specify the maximum size of a project folder on the volume. See “Setting/Changing the Project Quota” on page 46.

Export a project — move a project folder from the projects depot to the root of the volume and thus make it accessible to all computers having access to the volume. See “Exporting a Project” on page 49.

Move a project between volumes — move a project from one volume with Project Store support enabled to another or between volumes in the pool. See “Moving a Project Between Volumes” on page 50.

Lock a project — prevent editing of a project. See “Lock a Project” on page 51.

Force close a project — dismount a project from a client computer that is holding it open. See “Force Closing a Project” on page 52.

Additionally, if you have enabled project quotas, only administrators of Project Store can create new projects in the projects depot. See “Create a New Project as Administrator” on page 31.

Important: You can perform most of the above operations only on projects with Available status i.e. projects that are not mounted on another computer. You can force close a project, keeping in mind that all unsaved changes will be lost. For more information, refer to “Force Closing a Project” on page 52.

The Project Management page displays all projects in the projects depot. You can sort the columns of the list in ascending/descending order to sort the projects list by name, description, modification date, size,

Managing Projects

31

status, replication status (if Project Store is installed on a Tiger Series appliance and Replication and Tiering is enabled), owner and volume on which the project is stored.

Create a New Project as AdministratorProject Store allows administrators to create new projects in the depot, only when project quotas are enabled. In this case, Project Store users cannot create new projects, but are only able to work with existing ones and to manage their settings.

A Project Store administrator can create a new empty project or a new project from template (inheriting the template project type and folder structure, the template project contents, or both).

To create a new empty project as administrator:1. In the Administrative interface, click Project Management.

The Project Management page displays all projects in the projects depot of the volume.


32

2. In the top menu, click New.

Note: This button is not present, if you haven’t enabled project quotas.

The New Project dialog appears.

3. Enter a name for the new project.

4. Make sure that Empty is selected beside the name box.

5. (optional) Provide a brief description of the project to help you and other users discern the project among the other projects in the depot.

6. (optional) Add keywords to the project, to facilitate searching the projects database – you can add as many keywords as you like, each keyword must be separated by space.

7. In Quota, enter the maximum size of the project on the volume, using the drop-down box beside it to change the unit of measure.

8. In the Project Type drop-down box, select one of the following:

• Single-user Write – no parsers for detecting the project type are applied and the project can be mounted with Read & Write permissions on only one computer at a time.

• Avid Bin Locking Project – Project Store emulates Avid FS for the project and allows mounting the project with Read & Write permissions on multiple computers simultaneously, letting Avid restrict accesses to project bins that are currently in use.

• Multi-user Write – there is no emulation of the file system, but Project Store allows mounting the project with Read & Write permissions on multiple computers simultaneously.

Managing Projects

33

Warning: Unless the applications you use allow accessing the same project with Read & Write permissions simultaneously, setting the project type to Multi-user Write can lead to corruption of data in the project.

9. (optional) Select a preferred mount point (a drive letter or the C:\Volumes folder), which to be used on each Windows computer for mounting the project drive.

10.(optional) In the Volume drop-down box, select the volume on which to create the project as long as Project Store support is enabled on multiple volumes.

Note: If you don’t select a particular volume, Project Store stores it on the first volume in the list. In case the volume Project Store selects doesn’t have enough free space, you have to manually select a volume in the list.

11.Click OK.

A folder with the name of the project is created in the projects depot. If project permissions are disabled, the newly created project is accessible for work to any Project Store user. If project permissions are enabled, until you set permissions to the newly created project, no Project Store user will be able to access it. For details about setting permissions to a project, refer to “Setting Project Permissions” on page 42.

To create a new project from template as administrator:1. In the Administrative interface, click Project Management.


2. In the top menu, click New.


34

Note: This button is not present, if you haven’t enabled project quotas.



Managing Projects

35

4. Beside the name box, select From Template.

Project Store displays a list of all project that are set as templates.

5. In the list, select the project that you want to use as a template for the new project.

Important: If a template project is currently mounted with Exclusive rights, you cannot use it as a template.

6. Select “Copy content from template”, if you also want to copy the contents of the template project to the new project.

Note: Copying the contents of the template project can take significant time. Until the whole contents is copied to the new project, both the template and the new projects are with “locked” status.

7. Select “Copy permissions” if you want the new project to inherit the permissions of the template project.

Note: Copying permissions from a template project includes the owner of the project.


36


9. (optional) Add keywords to the project, separating each keyword with a space.

10.In Quota, enter the maximum size of the project on the volume, using the drop-down box beside it to change the unit of measure.

11.Specify a preferred mount point, which to be used on Windows computers for mounting the project drive as long as it is free.

12.(optional) In the Volume drop-down box, select the volume on which to create the project.

Note: If you don’t select a particular volume, Project Store stores it on the first volume in the list. In case the volume Project Store selects doesn’t have enough free space, you have to manually select a volume in the list.

13.Click OK.

A folder with the name of the project is created in the projects depot. If project permissions are enabled, but you haven’t copied the permissions of the template project, no Project Store user will be able to access the new project until you set permissions to it. For details about setting permissions to a project, refer to “Setting Project Permissions” on page 42.

Renaming a ProjectThe name of a project folder is used as a label of the drive that mounts on client computers. You can rename a project at any time as long as it is with Available status i.e. it is not mounted on another computer.

To rename a project:1. In the Administrative interface, click Project Management.

The Project Management page displays all projects in the projects depot.

Managing Projects

37

2. Find the project whose name you want to change and select its check box.

Tip: You can sort the columns of the list in ascending/descending order to more easily find the project.

3. Click Rename.

The Rename Project dialog appears.

4. Enter the new name of the project and click OK.

Deleting a ProjectThe owner of a project or an administrator of Project Store can delete a project folder as long as it with Available status (i.e. it is not mounted on any other computer) and it is not locked. Once you delete a project folder in Project Store, the hidden folder and all of its contents are deleted from the projects depot on the volume and cannot be restored.

To delete a project:1. In the Administrative interface, click Project Management.


2. Find the project that you want to delete and select its check box.


Note: To delete multiple projects simultaneously, select their check boxes and click Delete.


38

3. Click Delete.

4. Confirm that you want to delete the selected project(s).

Editing the Project DescriptionThe project description facilitates you in discerning one project from another. The description is also scanned by the Project Store’s search engine when displaying search results. You can change the description of a project at any time as long as a project is with Available status i.e. it is not mounted on another computer.

To add/edit the project description:1. In the Administrative interface, click Project Management.


2. Find the project whose description you want to change and click its name.

Managing Projects

39


Project Store opens the Project page for the selected project.

3. In the Description field, add a brief description of the project or edit the existing one.

4. Click Save.

Editing the Project KeywordsThe keywords associated with a project facilitate you when searching for a project using the Project Store’s search engine. You can add new keywords or delete current ones at any time, as long as the project is with Available status i.e. it is not mounted on another computer.


40

To add/edit the keywords of a project:1. In the Administrative interface, click Project Management.


2. Find the project whose keywords you want to change and click its name.

Managing Projects

41



3. In the Keywords field, do one of the following:

• To add a keyword, click in the Keywords box and type the desired keywords separated by spaces.

• To delete a keyword, select it in the Keywords box and delete it.

4. Click Save.


42

Setting Project PermissionsUnless Project Store is deployed without security, the access to each project folder is subject to authentication. You can authenticate yourself with the account you log on to Project Store with (either a domain account or an internal Project Store account). Until permissions of the project are set only its owner can mount it for viewing or editing. The owner of a project or a Project Store administrator can specify permissions defining who can access the projects and with what rights:

View — the user can mount the project with Read Only permissions only.

Edit — the user can mount the project with Read Only, Read & Write and Exclusive permissions, but cannot delete the project.

Owner — the user can mount the project with Read Only, Read & Write and Exclusive permissions, and can manage any of its settings and delete it.

Note: Only an administrator can change the owner of a project.

You can assign the above permissions to individual users or to user groups.

Note: When Project Store operates in Active Directory domain environment, to assign permissions to a user group, this group must be a sub-group of the existing group “projectStore Users” on the domain controller.

As you can set permissions both for a user and for the group this user is part of, Project Store performs the following check to decide which permissions to apply for the user:

• the permissions set for the user precede the permissions set for the group this user is part of;

• if you specify permissions for two or more user groups, of which a user is a member, but do not set the individual permissions of that user, Project Store uses the more restrictive permissions set for the group i.e. if one group has Edit permissions and the other has View permissions, the user will have View permissions only;

• the permissions set for a sub-group precede the permissions set for the group of which this sub-group is a member;

• if no permissions are set specifically for a user or a sub-group, Project Store applies the permissions set for the group.

Each time you switch the environment in which you deploy Project Store from domain to workgroup or vice versa, an administrator of Project Store has to reset the permissions of each project manually to allow users to access it.

To set project permissions:

Important: While setting the permissions of a project, it is with In Use status in the User interface and no computer can access it until you exit the Permissions interface.

Managing Projects

43

1. In the Administrative interface, click Project Management.


2. Find the project whose permissions you want to set and select its check box.


3. Click Permissions.


44

Important: You can change the permissions of a project only if it is with Available status i.e. is not mounted on another computer.

The Permissions dialog appears. When invoked for the first time it displays just the account of the user that has created the project and lists it as owner.

4. Do one of the following:

• To add users or groups to the list of users that have access to the project, in the Add People box enter the name of the user or group and in the drop-down box beside, specify what are the permissions of this user/group and click Add.

Note: Domain user accounts must be added with their domain.

• To remove a user or group from the list of users that have access to the project, click the Close button next to the user or domain group.

• To edit the permissions of a listed user or domain group, in the drop-down box beside the user/group name select the respective permission.

Important: You cannot set more than one user or group as owner of the project. Each time you specify a new owner, the permissions of the previous user/group that has been set as owner are automatically changed to Edit.

Managing Projects

45

5. In the Permissions dialog, click Save and then Close.

The new permissions are applied immediately.

Setting Preferred Mount Point of a ProjectWhen a client computer mounts a Project Store project for editing or viewing, the project is mounted on the computer as a local drive, using the following default mount point depending on the client computer operating system:

Windows — using the first available drive letter.

Mac OS X — in the /Volumes directory.

Linux — in the /mnt directory with an automatically created symbolic link /Volumes, which points to the /mnt directory.

A Project Store administrator can specify a universal mount point of a project on all Windows client computers - one and the same drive letter or a folder in the C:\Volumes directory.

Note: If you specify a drive letter as default mount point and it is already taken, the default mount point is used.

Important: You can set or change the preferred mount point of a project, only if it is with Available status i.e. is not mounted on another computer.

To set/change the preferred mount point of a project on Windows clients:1. In the Administrative interface, click Project Management.


2. Find the project whose preferred mount point you want to set/change and click its name.


46



3. In the “Preferred mount point (Windows only)” drop-down box, select either a drive letter or the C:\Volumes folder.

4. Click Save.

Setting/Changing the Project QuotaOnce project quotas are enabled in Project Store you can assign quotas or change the already set quotas of all projects in the depot. If you leave a project without quota or assign a quota that is bigger than the

Managing Projects

47

available free disk space or the size of the volume itself, the project size will not be limited. You cannot change the quota of a project to a size that is smaller than its current size.

To set/change the quota of a project:1. In the Administrative interface, click Project Management.


2. Find the project whose quota you want to set/change and click its name.


48



3. In Quota, enter the maximum size of the project on the volume, using the drop-down box beside it to change the unit of measure.

Tip: To remove the quota of a project, simply leave the Quota field empty.

4. Click Save.

Managing Projects

49

Exporting a ProjectWhen you need to access the files of a project not through Project Store (if you want to archive them, for example) instead of disabling Project Store support on the volume in order to unhide the projects depot, you can export the project. The export operation copies the project folder and all its contents to the root of the volume on which the depot is stored as long as there is enough free space. The new folder inherits the hierarchical structure of the project and contains all of its data and is accessible to all computers that can browse the volume.

If you have enabled support for Project Store on a volume pool, the exported folder is created on the volume on which the project in the project depot has been stored. If there isn’t enough free space on that volume, Project Store exports it to the root of the volume in the pool with least projects as long as there is enough free space on it. You can move projects stored on a volume pool between volumes, following the steps described in “Moving a Project Between Volumes” on page 50.

Important: You can export a project, only if it is with Available status i.e. is not mounted on another computer.

To export a project folder:1. In the administrative interface, click Project Management.

The Project Management page appears.

2. Select the project that you want to export.


Note: You can select multiple projects to export them simultaneously.

3. In the top menu, click Export and then confirm that you want to export the selected folder(s).

The folders are copied to the root of the volume on which they are.


50

Moving a Project Between VolumesWhen Project Store support is enabled on multiple volumes or on a volume pool, you can select on which volume to create each new project. Similarly, after a project is created in the projects depot, you can move it between the volumes in the pool or the volumes, on which Project Store support is enabled.

Important: You cannot move a locked project or a project mounted on another computer i.e. with In Use status.

To move a project folder between volumes:1. In the Administrative interface, click Project Management.

The Project Management page appears.

2. Select the project in the list and in the top menu, click Move.


Project Store opens the Move Project dialog.

3. In the Volume drop-down box, select the volume to which you want to move the selected project.

4. Click OK.

The project folder is move from its current volume to the selected volume.

Managing Projects

51

Lock a ProjectWhen you don’t want anyone to introduce any further changes to a project, you can lock it. By locking a project you provide only Read Only access to it, until the owner of a project or an administrator unlocks it.

Important: You can lock a project, only if it is with Available status i.e. is not mounted on another computer.

To lock/unlock a project:1. In the Administrative interface, click Project Management.


2. Find the project that you want to lock/unlock and click the project title link.


3. In the Project page, do one of the following:

• To lock the project, select the Locked check box and click Save.


52

• To unlock the project, clear the Locked check box and click Save.

Force Closing a ProjectAs a Project Store administrator you can force close any project opened for editing or just for viewing on a client computer. When you force close a project in the Project Store interface, you simply force the unmounting of the project folder from the client computer.

Important: Any unsaved changes to the project on the client computer are lost upon force closing it.

To force close a project:1. In the Administrative interface, click Project Management.


2. Find the project that you want to force close and in its badge, click the In Use link.

Optimizing the Project Store Workflow

53


The Users dialog appears. It displays information about all users that have mounted the project and the IP addresses of the computer(s) on which the project is mounted.

3. Click Force Close.

4. Confirm that you want to force close the project.

The project folder is unmounted from any computer that has mounted it for editing or viewing.

Optimizing the Project Store WorkflowThe administrator of Project Store can change several settings in order to optimize one or the other workflow in the Project Store environment:

Manage proxies — control proxies generation. See “Managing Proxies” on page 53.

Create project templates — set existing projects to serve as templates for future projects. See “Setting a Project as Template” on page 60.

Reset the projects database — clean all projects information such as project size, application type, number of files, users, etc. in case the database has been corrupted and displays incorrect results. See “Resetting the Projects’ Database” on page 63.

Rescan a project — schedule one or more projects for parsing, thus generating metadata information (video, audio and application information, project size and structure, objects in the project, etc.) in the projects depot database. See “Rescanning a Project” on page 64.

Managing ProxiesManaging the proxies means to enable or disable the generation of proxy media. By default, Project Store generates proxy media for all media files in the project folders in order to facilitate previewing projects’


54

contents without having to mount them. Proxies are generated by the pre-installed parsers for most media files.

When proxies generation is enabled, Project Store scans for media without proxies in a project each time that project is unmounted from the last client computer that has mounted it for editing. You can force the generation of proxies for a project with no proxy media generated so far, by rescanning it (see “Rescanning a Project” on page 64).

Note: If the project already contains proxy media, to force the generation of proxies for the project, you should first clear its current proxies, following the steps on page 59.

Project Store also allows you to manually manage proxies by monitoring the progress of the queue and of individual proxy files, by pausing and starting the processing of the proxies queue. You can also delete all generated proxies or just the proxies associated with a specific project in the Project Management page.


55

To enable proxies generation:1. In the Access the administrative, click General Settings.

2. In Proxy Generation Options, select “Generate proxies when idle”.

3. Click Save.


56

To disable proxies generation:1. In the administrative interface, click General Settings.

2. In Proxy Generation Options, select “Do not generate proxies”.

3. Click Save.

To view the progress of proxies generation:In the administrative interface, click Proxies.

The Proxies page appears. It displays the list of all files queued for proxies generation. Next to each queued file in the list you can view its size, type, the project to which it belongs, status and approximate


57

time left to complete. You can sort the columns of the list in ascending/descending order in order to rearrange it.


58

To pause/resume the proxies queue:1. In the administrative interface, click Proxies in the left pane.

The Proxies page appears.


• Click “Pause Queue” to pause the processing of proxies generation.

• Click “Resume Queue” to resume processing proxies generation.

To delete all proxies in the projects depot:

Note: You can also delete the proxies generated for a specific project only.


59

1. In the administrative interface, click Proxies.

The Proxies page appears.

2. Click Delete all.

3. Confirm that you want to delete all proxies in the depot.

To clear the proxies of a project:

Important: You can clear the proxies of a project, only if it is with Available status i.e. is not mounted on another computer.


60

1. In the Administrative interface, click Project Management.


2. Find the project whose proxies you want to remove and select its check box.


Note: You can select multiple projects with Available status, to clear their proxies simultaneously.

3. In the top menu, click Clear Proxies.

The proxies of the project are deleted.

Setting a Project as TemplateTo facilitate users when creating new projects, Project Store allows you to set any existing project as template for future projects. When you create a new project from a template, you inherit the type and the folder structure of the template. Additionally, you can also select to copy the contents of the template project or inherit its permissions, or both.

Important: You can set a project as template, only if it is with Available status i.e. is not mounted on another computer.


61

To set a project as a template:1. In the Administrative interface, click Project Management.


2. Find the project that you want to set as a template and click its title.


62




• To set the project as a template, select the Template check box.


63

• To remove the project from the list of templates, clear the Template check box.

4. Click Save.

Resetting the Projects’ DatabaseThe projects’ database holds information about:

• proxy media;

• metadata generated by parsers – project structure, project application type, etc.;

• Project Store user and administrator accounts (user name and password);

• project size, number of files in the project folder, etc.;

Should the projects database get corrupted (fail to correctly list search results or to display information about media and projects), you can clean it and queue it for re-generation, without any risk for the actual data in the projects’ depot. The cleaned database is updated with information about a project when that project is mounted and then dismounted on a client computer, or when you rescan it (see “Rescanning a Project” on page 64).

Important: After resetting the projects’ database, some settings like project quota, permissions, last mount state are reverted to their defaults and you might need to configure them anew.

You can also choose to reset the projects’ database when you’ve set the permissions of Project Store users/administrators in such a way that no user is able to log on to Project Store and work with projects. In this case, Project Store restores the pre-configured administrator’s account (if it has been deleted) and the user name of each Project Store user/administrator but with a blank password, prompting each user to provide a new password for his/her account.

Important: Project Store can restore only the accounts of users/administrators associated with a project (owners of a project or users with access permissions to a project). All other Project Store accounts are permanently deleted.

Until the projects’ database is regenerated, all available information is retrieved from the disks instead of the database. This excludes proxy media, which has to be generated anew.


64

To reset the database of a project:1. In the administrative interface, click General Settings.

The General Settings page appears.

2. Under Maintenance, click Reset DB and then confirm that you want to clean the projects database and queue it for regeneration.

The database is reset and all proxy media and information about the project (size, application type, number of files, etc.) are deleted. This information can be regenerated for a project once a user mounts and then dismounts it. You can also regenerate this information for one or more projects by rescanning them, following the steps in “Rescanning a Project” on page 64.

Rescanning a ProjectBy default, each time a project is dismounted from a client computer, the Project Store parsers scan it in order to update information about files in the project, such as video codecs, frame rate, audio sample rate, application used, project structure, etc. Additionally on dismount the projects database is updated with


65

information about the project size, number of files in the project, user accounts associated with the project. You can force the parsing of a project without having to mount and then dismount it from a client computer and thus update metadata information about it in the projects depot database.

You can also rescan a project in order to force the generation of proxy media in it. You can do it only if the project doesn’t contain any proxy media generated already. If it does, you should first clear its proxies and only after that rescan it.

Note: You can rescan a project, only if it is with Available status i.e. is not currently mounted on any client computer.

To rescan a project:1. In the Administrative interface, click Project Management.


2. Find the project that you want to rescan and select its check box.


Note: To rescan multiple projects simultaneously, select their check boxes.

3. Click Rescan.

Downloading the Projects List as a .csv FileTo facilitate you in keeping track of your projects, Project Store allows you to download the list of all projects in the depot as a comma separated values (.csv) file. The file contains the following information about each project in the depot - name, description, time of last modification, size, status and volume, on which the project is stored.

Note: Data in the .csv file is arranged the same way as it appears in the web interface. To rearrange it, before downloading the .csv file sort the desired columns in ascending or descending order by clicking their headers.


66

To download the projects list as a .csv file:1. In the Administrative interface, click Project Management.


2. Sort the projects list the way you want it to appear in the .csv file by clicking the header of the respective column and then click CSV.

Depending on the settings of your web browser, the .csv file either downloads automatically to your default location for downloaded files or you are prompted to select a location yourself.

Viewing the Activity LogIn the administrative interface of Project Store you can view a log of all activity related to Project Store:

• Project Store settings - enabled/disabled for a volume, permissions enabled/disabled;

• user settings - created, deleted, role changed;

• project settings - project created, deleted, mounted, unmounted, moved from one volume to another;

By default, the activity log displays all events sorted in descending order starting from the most recent ones. You can filter the results displayed in the log by time period, user, project and type of event.

Viewing the Activity Log

67

To view the activity log:1. In the administrative interface, click Activity Log.

2. You can sort the columns of the list in ascending/descending order or filter the results, by selecting the desired criteria for the filter in the corresponding fields and then clicking Apply.


68

Working with Project Store

The User Interface . . . . . . . . . . . . . . . . . . . . . . . . . 72

Resetting the Password of Your Project Store Account . 74

Searching The Projects Depot . . . . . . . . . . . . . . . . . . 74

Working with Projects . . . . . . . . . . . . . . . . . . . . . . . 77

Editing Project Settings . . . . . . . . . . . . . . . . . . . . . . 96


70

Any Tiger Client computer that can access the volumes/volume pool, on which support for Project Store is enabled, can create new projects and mount their own or other users’ project folders exclusively, with Read & Write permissions or for previewing only.

Important: To be able to work with Project Store from a Tiger Client computer, this computer must be connected to the storage server on which support for Project Store is enabled. For more information, refer to the Administration Guide of your Tiger Series product.

When Project Store is deployed with disabled security, access to project folders depends only on the access to the volume on which the projects depot is and on the status of the project (Available or In Use). When security is enabled, access to any given project folder depends on the permissions set for your domain or Project Store account.

To facilitate you when browsing the projects depot for your or others’ projects, Project Store integrates a search engine that displays results based on project name, keywords, description, files and objects names, etc. You can also browse proxy media generated for all projects and thus preview the contents of a project your account has access to without having to mount it.

Accessing the User Interface of Project StoreTo access the User interface, you have to log on to Project Store with an account that is either a member of the “projectStore Users” group on the domain controller (when Project Store is deployed in an Active Directory domain), or an internal Project Store user account, created by an administrator of Project Store (when Project Store is deployed in workgroup environment). See “Managing Project Store User Accounts and Groups” on page 19.

Note: If the “projectStore Users” group doesn’t exist on the domain controller, you have to manually create it. If you want to use the accounts in a different group on the domain controller, contact Tiger Technology support for assistance.

Important: If a user account is a member of both the Admin group and the User group, this user always gains access to the Administrative interface only.

71

To access the user interface from a Windows or Mac OS X Tiger Client:1. In the Tiger Client tray application/menulet, click Project Store and then click the IP address of the

storage server running Project Store.

2. Enter a user name and password, then click Login.

For more details about the interface, refer to “The User Interface” on page 72.

To access the user interface from a Linux Tiger Client:1. In the address bar of a web browser, type this:

http://[IP address or name of the computer with Project Store installed]:8480

Important: To access the user interface using the computer’s name instead of IP address, a DNS server on the network must resolve the IP address to its domain name.


72

2. Enter the user name and password, then click Login.

For more details about the interface, refer to “The User Interface” on page 72.

To log out Project Store:

Important: After you log out Project Store, all project folders currently mounted for viewing or editing are automatically unmounted and all unsaved changes are lost.

In the top band of the web interface, click Log out.

The User InterfaceThe User interface of Project Store is the workplace for actually working with projects.

The User Interface

73

The User interface offers you three views:

Recently accessed projects — the default view, lists the last 10 most recently modified by you projects to which you have access (your own projects or projects shared with you) sorted in descending order by last access time.

My Projects — lists all your projects sorted in descending order by name.

Shared with Me — lists all other users’ projects that are shared with you sorted in descending order by last access time.

Regardless of the view displayed, the top band of the User interface gives you information about the currently logged user, the total capacity of the projects depot, the available free space (these values are also illustrated by a progress bar).

Below the Project Store logo, you can also view the version of Project Store running on the metadata controller. The top band of the interface also allows you to search the projects (see “Searching The Projects Depot” on page 74) and to create new projects or import existing ones (see “Working with Projects” on page 77). In the upper right corner are the buttons that allow you to log out Project Store, to reset the password for your account, to display information about the software, to access the appliance interface and to access the Project Store documentation.

All projects in the User interface are displayed with a tile, which differs depending on the permissions for your account.

The project tile shows you the project name, owner, type, preferred mount point, size, last access date, background tasks running at the moment, whether there is proxy media generated for the project. Additionally the project icon shows you the status of the project for your account:

the project can be mounted on your computer


74

Tip: Click the project name link to open the project page (see “Preview a Project without Mounting It” on page 91);

Resetting the Password of Your Project Store AccountBeside Project Store administrators, each Project Store user can reset the password of his/her Project Store account.

To reset the password of your Project Store account:1. In the upper right corner of the User interface, click Reset Password.

The Reset Password dialog appears.

2. Enter the new password in the corresponding fields and click OK.

Searching The Projects DepotTo facilitate you in finding projects and data in the projects depot, Project Store provides you with a search engine. When initiating a search from the Administrative interface, Project Store displays results based only on project name, description and keywords. When the search is initiated from the User interface, Project Store also searches for data in the projects based on metadata generated by the parsers (file name, format, video/audio properties, etc.), but displays only results in projects for which your account has at least Read Only permissions.

the project is mounted on another computer

the project is locked

Searching The Projects Depot

75

Note: Project Store parses each project, which has been mounted for editing, when it is dismounted. You can also force the parsing of a project by rescanning it.

Check the table below for details about what and how can be searched in Project Store:

searches for results in query format*/valid query example

Admin interface

User interface

Case sensitive

Exact match*

project name(Cat 123)

alphanumeric:cat1

- -

project description(Cat food commercial 2)

alphanumeric:cat

- -

project keyword(“siamese cat”)

alphanumeric:“cat”

- -

file name(“cat324.mov”)

alphanumeric:“cat32”

- - -

file format(“cat324.mov”)

alphanumeric:“.mov”, “mov”

- - -

file duration(“cat324.mov” with duration 1 min 38 seconds and 19 milliseconds)

“0:01:38:19” - -

video file frame width(“cat324.mov” video file with frame width of 852 pixels)

852 - -

video file frame height(“cat324.mov” video file with frame height of 480 pixels)

480 - -

video file aspect ratio(“cat324.mov” video file with screen aspect ratio 0:1)

0:1 - -

video file frame rate(“cat324.mov” video file with a frame rate of 25 frames per second)

25.00 fps -

audio codec(“cat324.mp3” audio file using mp3 codec)

MP3 (MPEG audio layer 3) -


76

* When searching for more than one keyword, your query must always be an exact match of the searched item.

All search results are sorted in alphabetical order. You can filter the results by choosing to display just the projects, the objects (bins, clips, sequences found in video editing applications projects, etc.) or the files.

To search the projects depot:1. In the User interface, enter a search term in the search box.

2. Press Enter.

In the left pane, Project Store displays all results matching the search criteria you have entered. Clicking a result in the left pane, allows you to preview its details in the Preview pane. For more details,

audio sample rate(“cat324.mp3” audio file using a rate of 44 100 samples per second)

44.100000 KHz -

Number of audio tracks(“cat324.mp3” audio file using just 1 audio track)

1 - -

Number of channels per tracks(“cat324.mp3” audio file using 2 channels per track)

2 - -

searches for results in query format*/valid query example

Admin interface

User interface

Case sensitive

Exact match*

Working with Projects

77

see “Preview a Project without Mounting It” on page 91. To filter the results by projects, objects or files, click the respective tab above the list with search results.

Tip: To clear the search results view and get back to the default view, click the Project Store logo in the upper left corner.

Working with ProjectsFrom a Tiger Client computer, you can work with projects stored in the projects depot in the following ways:

• Create a new empty project (see “Create a New Empty Project” on page 78).

• Create a new project from template (see “Create a New Project from Template” on page 80).

• Import an existing project into the Project Store depot (see “Import an Existing Project into Project Store” on page 83).

• Export a project as a folder to the root of the volume (see “Exporting a Project” on page 85).

• Mount a project with Read Only permissions to read and copy data from it (see “Mount a Project for Viewing” on page 86).

• Mount a project with Read & Write permissions – depending on the type of the project, other computers may also be able to mount it for editing (Avid Bin Locking or Multi-user Write project types) or just for viewing (see “Mount a Project for Editing” on page 87).

• Mount a project for editing with Exclusive permissions i.e. not letting any other computer mount it for editing or viewing until you unmount it regardless of the type of the project (see “Mount a Project for Editing” on page 87).

• Lock a project, allowing only Read Only access to it even to its owner (see “Lock a Project” on page 89).

• Edit project settings such as name, description, keywords, type and allow using it as template for other projects (see “Editing Project Settings” on page 96).

• Close a project (see “Close a Project” on page 89).

• Delete a project (see “Delete a Project” on page 90).

• Preview the settings and contents of a project (see “Preview a Project without Mounting It” on page 91).

Project Store has an intuitive user interface that displays just the options that are currently available for you for each project – these depend on the status of the project (In Use or Available) and on the permissions your account has for the specific project. The interface updates the information about projects dynamically and there’s no need to refresh your browser in order to view most current information.


78

Depending on the status of the project for your computer, you can perform the following:

* Multi-user Write or Avid Bin Locking projects.

** Except if the project is mounted exclusively on another computer.

Create a New Empty ProjectWhen you select to create a new empty project besides specifying the name and type of the project, you can also add description and keywords to facilitate finding the project, and specify preferred mount point of the new project on Windows computers.

Note: Only Project Store administrators can create projects, when project quota setting is enabled in Project Store. For steps, refer to “Create a New Project as Administrator” on page 31.

Available In Use(RW on another

machine)

In Use(RO on another

machine)

In Use(RW on

own machine)

In Use(RO on

own machine)

Locked

Edit * -

Edit exclusively - - -

Read **

Close - - -

Rename - - - -

Delete - - - - -

Move - - - - -

Lock - - - - -

Make template - - - -


79

To create a new empty project:1. In the User interface, click New Project.

Note: The New Project button is not present in the user interface when project quotas are enabled in Project Store and only Project Store administrators can create new projects (see “Create a New Project as Administrator” on page 31).



3. Make sure that Empty is selected beside the name box.


5. (optional) Add keywords to the project, to facilitate searching the projects database – you can add as many keywords as you like, each keyword must be separated with a space.


• Single-user Write – the project can be mounted with Read & Write permissions on only one computer at a time.

• Avid Bin Locking Project – Project Store emulates Avid FS for the project and allows mounting the project with Read & Write permissions on multiple computers simultaneously, letting Avid restrict accesses to project bins that are currently in use.



80


7. (optional) Select a preferred mount point (a drive letter or the C:\Volumes folder), which to be used on each Windows computer when mounting the project drive.

8. (optional) In the Volume drop-down box, select the volume on which to create the project as long as Project Store support is enabled on multiple volumes or on a volume pool.

Note: In case you don’t select a particular volume and Project Store support is enabled on a volume pool, Project Store attempts to store the project on the volume with less folders. If support is enabled on multiple volumes, Project Store stores it on the first volume in the list. In case the volume Project Store selects doesn’t have enough free space, you have to manually select a volume in the list.

9. Click OK.

A folder with the name of the project is created in the projects depot. If project permissions are disabled, the newly created project is accessible for work to any user. If project permissions are enabled, until you set permissions to the newly created project, only you as owner can access it. For details about setting permissions to a project, refer to “Setting Project Permissions” on page 104.

Create a New Project from TemplateIf you choose to create a new project based on template, your new project will be the same type as the template project and will inherit its folder structure. You can also select to copy the contents of the template project or inherit its permissions, or both. The description, keywords and preferred mount point setting are optional and should be specified manually for each new project. Project Store allows you to set any existing project as a template for new projects. For more details about setting a project as template, see “Setting a Project as Template” on page 102.

Important: Until the creation of the new project is fully finished, both the new project and the template project remain with In Use status for other computers.

Note: Only Project Store administrators can create projects, when project quota setting is enabled in Project Store. For steps, refer to “Create a New Project as Administrator” on page 31.


81

To create a new project from template:1. In the User interface, click New Project.

Note: The New Project button is not present in the user interface when project quotas are enabled in Project Store.




82

3. Beside the name box, select From Template.

Project Store displays a list of all project that are set as templates to which your account has at least View access.

4. In the list, select the project that you want to use as a template for the new project.

Important: If a template project is currently mounted with Exclusive rights, you cannot use it as a template.

5. Select “Copy content from template”, if you also want to copy the contents of the template project to the new project.

Note: Copying the contents of the template project can take significant time. Until the whole contents is copied to the new project, both the template and the new projects are with “locked” status.

6. Select “Copy permissions” if you want the new project to inherit the permissions of the template project.

Note: Copying permissions from a template project includes the owner of the project.


83


8. (optional) Add keywords to the project, separating each keyword with a space.

9. (optional) Specify a preferred mount point, which to be used on Windows computers for mounting the project drive.

10.(optional) In the Volume drop-down box, select the volume on which to create the project.


11.Click OK.

A folder with the name of the project is created in the projects depot. If project permissions are disabled, the newly created project is accessible for work to any user. If project permissions are enabled, until you set permissions to the newly created project, only you as owner can access it. For details about setting permissions to a project, refer to “Setting Project Permissions” on page 104.

Import an Existing Project into Project StoreTo facilitate you in migrating projects that already exist on the volume to the projects depot, Project Store allows you to import them by copying an existing folder into the repository.

When importing a folder into the projects depot, Project Store copies the folder and its data to the repository on a selected volume. The project is named after the folder that has been copied and the imported project keeps its security settings.

When support for Project Store is enabled on multiple volumes, you can select on which volume to import the project. Project Store doesn’t allow you to import folders that have the same name as an existing project in the projects depot. In this case you have to either rename the folder before importing it or import it on another volume.

When Project Store support is enabled on a volume pool and you import an ambiguous folder (a folder with the same name existing in the same location on two or more volumes in the pool), it contains the merged contents of all ambiguous folders with the same name, but has the attributes of the ambiguous folder that is on the volume first detected by the metadata controller service at the time you perform the import operation.

Upon import all imported data is indexed. You can also specify project description, keywords, preferred mount point (on Windows) and on what volume to create the project.

Important: When project quota setting is enabled in Project Store, you cannot import projects into the depot.


84

To import an existing project into the repository:1. In the User interface, click Import.

Note: The button is inactive, if project quotas are enabled in Project Store.

The Import Project dialog appears.

2. In the “From Volume” drop-down box, select the volume from which to import the project.

Note: When support for Project Store is enabled on a volume pool, the dialog lists the projects on all volumes in the pool.

3. In the pane, navigate to and select the folder, which you want to import.

4. In the “To Volume” drop-down box, select the volume on which to import the project.



85


6. (optional) Add keywords to the project, separating each keyword by space.

7. (optional) Select a preferred mount point (a drive letter or the C:\Volumes folder), which to be used on each Windows computer for mounting the project drive.

8. Click Import.

Note: Importing a folder or a project file with all associated data can take significant time.

A project with the name of the folder is created in the projects depot. It contains all data from the imported folder. If project permissions are disabled, the imported project is accessible for work to any user. If project permissions are enabled, until you set permissions to the imported project, only you as owner can access it. For details about setting permissions to a project, refer to “Setting Project Permissions” on page 104.

Exporting a ProjectWhen you need to access the files of a project not through Project Store (if you want to archive them, for example) instead of disabling Project Store support on the volume in order to unhide the projects depot, you can export the project. The export operation copies the project folder and all its contents to the root of the volume on which the depot is stored as long as there is enough free space. The new folder inherits the hierarchical structure of the project and contains all of its data and is accessible to all computers that can browse the volume.

If you have enabled support for Project Store on a volume pool, the exported folder is created on the volume on which the project in the project depot has been stored. You can move projects stored on a volume pool between volumes, following the steps described in “Moving a Project Between Volumes” on page 109.

Important: Only the owner of a project can export a project and only if the project is with Available status.


86

To export a project folder:1. In the User interface, find the project, which you want to export.

2. In the badge of the project, click its title.


3. In the top menu, click Export and then confirm that you want to export the project.

The project folder is copied to the root of the volume on which it is stored.

Mount a Project for ViewingOnce you mount a project folder for viewing (with Read Only permissions), it is mounted on your computer as a local drive, but you cannot introduce any changes to it – you can just copy data from it to another location (a project folder mounted for editing, for example).

A project folder can be mounted for viewing on multiple computers as long as it is not mounted Exclusively on another machine.

Tip: To view who has mounted the project and with what permissions, click the In Use link.

Note that if changes are introduced in the project from the computer that has mounted it for editing, all computers that are just viewing the project detect these changes only after re-mounting the project folder.


87

Important: (Avid only) You can open an Avid project, stored in a Project Store project folder, only if you have mounted it for editing. When the project folder is mounted with Read Only access, you will be able to open the project’s Bins only.

To mount a project folder for viewing:1. Find the project that you want to mount for viewing.

2. In the project’s badge, click Read.

Note: If the project is mounted Exclusively on another computer, this button is missing.

The project folder mounts as a local drive on your computer. If no preferred mount point is specified, the project is mounted in the default mount point for the respective platform:

• (Windows) using the first available drive letter.

• (Mac OS X) in the /Volumes directory.

• (Linux) in the /mnt directory with an automatically created symbolic link /Volumes, which points to the /mnt directory.

Mount a Project for EditingBefore beginning work with your desired application on the project folder that exists in the project depot, you must first mount the project folder as local drive on your computer. Project Store provides you with several options for mounting a project for editing. When the project type is set to “Single-user Write” only one computer can mount it with Read & Write permissions at a time and the project status must be “Available”. When the project type is “Avid Bin Locking” or “Multi-user Write” multiple computers can mount it for editing even if the project status is “In Use”. Note that in this case preventing data corruption is up to the application you use for access to the project.

Regardless of the type of the project, you can mount it Exclusively (mount it for editing with Exclusive rights), which means that no other computer can mount it neither for editing, nor for viewing until you close it on your computer.

Additionally, if a project is locked, it cannot be mounted for editing on any computer until the owner of the project or an administrator unlocks it.


88

To mount a project for editing:1. Find the project that you want to mount for editing.

2. In the project’s badge, click Write.

Note: This button is not present, if a “Single-user Write” project is with “In Use” status, if the project is mounted “Exclusively” on another computer, or if the project is locked.





To mount a project Exclusively:1. Find the project that you want to mount for viewing.

2. In the project’s badge, click Exclusive.

Note: This button is not present, if the project is with “In Use” status or the project is locked.





Note: To allow access to the project again, you must close the project (see “Close a Project” on page 89).


89

Lock a ProjectWhen you don’t want anyone to introduce any further changes to a project, you can lock it. By locking a project you provide only Read Only access to it, until it is again unlocked. Locking a project can be useful when you want to set a project as template.

Important: Only the owner of a project or a Project Store administrator can lock/unlock a project. You cannot lock/unlock a project with “In Use” status.

To lock/unlock a project:1. Find the project that you want to lock.

2. Click the project title link.

3. In the Project page, do one of the following:

• To lock the project, select the Locked check box and click Save.

• To unlock the project, clear the Locked check box and click Save.

Close a ProjectYou can close a project you have opened for editing or just for viewing. When you close a project in the Project Store interface, you simply unmount the project drive from your computer. That is why, before closing a project, which you have edited, make sure that you have closed it in the editing application first, as any unsaved changes will be lost once you unmount the project drive from your computer.

You cannot close a project mounted on another computer. If a computer is holding a project open, you can force close it. Force closing a project unmounts the project from the computer and any unsaved changes in the project are lost.

Important: Project Store automatically closes (unmounts) all open projects on your computer on system reboot.


90

To close a mounted project:1. Find the project that you want to close.

2. In the badge of the project that you want to close, click Close.

Note: This button is not present, if the project is mounted on another machine. To see how to unmount a project from another computer, refer to Force Closing a Project below.

The project drive is unmounted from your computer.

To force close a mounted project:

Important: Force closing a project unmounts the project from the computer and any unsaved changes to the project are lost.

1. Find the project that you want to force close.

2. In the badge of the project that you want to force close, click the In Use link.

The Users dialog appears. It displays information about all users that have mounted the project.

3. Click Force Close.

4. Confirm that you want to force close the project.

The project folder is unmounted from any computer that has mounted it for editing or viewing.

Delete a ProjectThe owner of a project or an administrator of Project Store can delete a project folder as long as it is not mounted on any computer (it is with Available status) and it is not locked. Once you delete a project folder


91

in Project Store, the hidden folder and all of its contents are deleted from the projects depot on the volume and cannot be restored.

To delete a project:1. In the User interface, find the project, which you want to delete.



3. Click Delete.

Project Store prompts you to confirm that you want to delete the project folder and all its contents permanently.

4. To confirm, select “I understand the consequences” and click Yes.

Preview a Project without Mounting ItProject Store allows you to preview a project even if you are accessing the user interface from a non-Tiger Client computer, as long as your account has permissions for the project.


92

Project Store offers you two options for previewing a project:

Project Preview panel — gives you general information about the project such as name, owner, size, number of files and folders, preferred mount point (if any), description, keywords associated with the project and a list of subprojects (if any).

Project page — all details from the Project Preview panel, including:

• detailed statistics about the size and type of all files in the project;

• the settings of the project – type (Single-user Write, Multi-user Write, Avid Bin Locking), locked, set as template, preferred mount point on Windows;

• Metadata – the project description and the full list of keywords and possibility to edit them;

• Views – allows you to filter the contents of the project by files/folders, media, objects and preview each element displayed in the Details panel.


93

To preview general project information:1. In the User interface, select the view (Recently Accessed, My Projects or Shared with Me) to filter the

list of projects available for your account.

2. In the list, select the badge of a project.

Project Store displays the Project Preview panel for the selected project. You can click the title of the project to view more details and preview its contents in the Project page.

To preview project settings, statistics and contents:1. In the User interface, find the project whose settings, statistics or contents you want to preview.


Project Store opens the Project page for the selected project. It displays the settings of the project, detailed statistics about the number, size and type of the files and folders in it, the description and


94

keywords associated with the project. The icon in the upper left corner shows you what permissions you have for the project and if its locked for editing.

3. To preview the contents of the project, do one of the following:

• To preview the hierarchical structure of the project, click Files/Folders and then browse the tree as you would in the file browser of your operating system. Selecting an item in the tree displays detailed information and/or preview of the item in the Preview panel.


95

• To preview just the media files in the project, click Media – Project Store displays a list with all media files detected in the project each with an icon designating its type (video, audio, image or image sequence). Selecting a file displays its details in the Preview panel and allows you to preview it (play a video or audio clip, an image sequence, etc.). Below the preview panel you can view more details about the selected file.

Note: When the media tab lists media files, but doesn’t allow you to preview them in the preview panel, either there is no proxy media generated yet, or the installed parsers detect the media files, but cannot generate proxy media for them.

• To preview objects (such as Adobe Premiere project, for example) as detected by the respective pre-installed parser, click Objects – Project Store tree view(s) with the hierarchy of the objects as detected by the parsers. Selecting an element in the tree, displays its details in the Preview pane.


96

Note: Project Store parses each project, which has been mounted for editing, when you dismount it. You can also force the parsing of a project by rescanning it.

Editing Project Settings

Rename a ProjectThe name of a project is used as a label of the drive that mounts on your computer. The name of the project folder can be different from the name of the project in it. Only the owner of a project or an administrator can edit its name.

Note: To edit the name of a project, it must be with Available status i.e. it must not be mounted on any other computer.

To rename a project:1. In the User interface, find the project whose name you want to change.




97

3. Click Rename.

The Rename Project dialog appears.

4. Enter the new name of the project and click OK.

Editing the Project DescriptionThe project description facilitates you in discerning one project from another. The description is also scanned by the Project Store’s search engine when displaying search results. You can change the description of a project at any time. To edit the description of a project, it must be with Available status i.e. it must not be mounted on any other computer.

Note: Only the owner of a project and users with Edit permissions can change the description of a project.


98

To add/edit the project description:1. In the User interface, find the project whose description you want to change.



3. In the Description field, add a brief description of the project or edit the existing one.

4. Click Save.


99

Editing the Project KeywordsThe keywords associated with a project facilitate you when searching for a project using the Project Store’s search engine. You can add new keywords or delete current ones at any time. To edit the keywords of a project, it must be with Available status i.e. it must not be mounted on any other computer.

Note: Only the owner of a project and users with Edit permissions can change the keywords of a project.

To add/edit the keywords of a project:1. In the User interface, find the project whose keywords you want to change.




100

3. In the Keywords field, do one of the following:

• To add a keyword, click in the Keywords field and type the desired keywords separated by spaces.

• To remove a keyword, select the keyword and delete it.

4. Click Save.

Editing the Project TypeYou can change the type of a project at any time. Keep in mind that if the project already contains data, changing its type may obstruct its usage and can even lead to data corruption. For example, you change the type of a project from Avid Bin Locking to Multi-user Write, you will remove the Avid FS emulation and Avid will no longer supervise which bins are currently available for use, etc. To edit the type of a project, it must be with Available status i.e. it must not be mounted on any other computer.

Note: Only the owner of a project and users with Edit permissions can change the type of a project.


101

To edit the type of a project:1. In the User interface, find the project whose type you want to change.




• Single-user Write – no parsers for detecting the project type are applied and the project can be mounted with Read & Write permissions on only one computer at a time.

• Avid Bin Locking – Project Store emulates Avid FS for the project and allows mounting the project with Read & Write permissions on multiple computers simultaneously, letting Avid restrict accesses to project bins that are currently in use.


102



4. Click Save.

Setting a Project as TemplateTo facilitate you in creating new projects, Project Store allows you to set any existing project as template for future projects. When you create a new project from a template, you inherit the type and the folder structure of the template. Additionally, you can also select to copy the contents of the template project or inherit its permissions, or both. To set a project as template or remove it from the list of template projects, it must be with Available status i.e. it must not be mounted on any other computer.

Note: Only the owner of a project and users with Edit permissions can set a project as template or remove it from the list of template projects.


103

To set a project as a template:1. In the User interface, find the project, which you want to set as template.




• To set the project as a template, select the Template check box.


104

• To remove the project from the list of templates, clear the Template check box.

4. Click Save.

Setting Project PermissionsUnless Project Store is deployed without security, the access to each project folder is subject to authentication. You can authenticate yourself with the account you log on to Project Store with (either a domain account or an internal Project Store account). Until permissions of the project are set only its owner can mount it for viewing or editing. The owner of a project or a Project Store administrator can specify permissions defining who can access the projects and with what rights:

View — the user can mount the project with Read Only permissions only.

Edit — the user can mount the project with Read Only, Read & Write and Exclusive permissions, but cannot delete the project.

Owner — the user can mount the project with Read Only, Read & Write and Exclusive permissions, and can manage any of its settings.

Note: Only an administrator can change the owner of a project.

You can assign any of the above permissions to both individual users and user groups.

Note: When Project Store operates in Active Directory domain environment, to assign permissions to a user group, this group must be a sub-group of the existing group “projectStore Users” on the domain controller.

As you can set permissions both for a user and for the group this user is part of, Project Store performs the following check to decide which permissions to apply for the user:

• the permissions set for the user precede the permissions set for the group this user is part of;

• if you specify permissions for two or more user groups, of which a user is a member, but do not set the individual permissions of that user, Project Store uses the more restrictive permissions set for the group i.e. if one group has Edit permissions and the other has View permissions, a member of both groups has View permissions only;

• the permissions set for a sub-group precede the permissions set for the group of which this sub-group is a member;


105

• if no permissions are set specifically for a user or a sub-group, Project Store applies the permissions set for the group.

Each time you switch the environment in which you deploy Project Store from domain to workgroup or vice versa, an administrator of Project Store has to reset the permissions of each project manually to allow users to access it.

To set project permissions:

Important: To change the permissions of a project, it must be with Available status. While setting the permissions of a project, it is with In Use status in the User interface and no computer can access it until you exit the Permissions interface.

1. In the User interface, find the project whose permissions you want to change.




106

3. Click Permissions.

The Permissions dialog appears. When invoked for the first time it displays just the account of the user that has created the project and lists it as owner.


• To add users or groups to the list of users that have access to the project, in the Add People box, enter the user name or group name and in the drop-down box beside, specify what are the permissions of this user/group, then click Add.

Note: Domain user accounts must be added with their domain.

• To remove a user or group from the list of users that have access to the project, click the Close button next to the user or group and confirm that you want to remove it from the list.

• To edit the permissions of a listed user or group, in the drop-down box beside the user/group name select the respective permission.

5. In the Permissions dialog, click Save and then Close.

The new permissions are applied immediately.


107

Setting Preferred Mount Point of a ProjectWhen a client computer mounts a Project Store project for editing or viewing, the project is mounted on the computer as a local drive, using the following default mount point depending on the client computer operating system:

• Windows – the first available drive letter.

• Mac OS X - /Volumes directory.

• Linux - /mnt directory with an automatically created symbolic link /Volumes, which points to the /mnt directory.

When creating a new project, you can specify a preferred mount point (a drive letter or the C:\Volumes folder) to be used on all client computers that mount the project. If the drive letter is already taken, the default mount point is used.

You can set or change the preferred mount point of a project at any time as long as the project is with Available status i.e. it must not be mounted on any other computer.

Note: Only the owner of a project and users with Edit permissions can change its preferred mount point.


108

To set/change the preferred mount point of a project:1. In the User interface, find the project whose preferred mount point you want to change.



3. In the “Preferred drive letter (Windows only)” drop-down box, select a drive letter or the C:\Volumes directory.

4. Click Save.


109

Moving a Project Between VolumesWhen Project Store support is enabled on multiple volumes or on a volume pool, you can select on which volume to create each new project. Similarly, after a project is created in the projects depot, you can move it between the volumes in the pool or the volumes, on which Project Store support is enabled.

Note: Only the owner of a project or an administrator of Project Store can move a project folder as long as it is not mounted on any computer (it is with Available status) and it is not locked.

To move a project folder between volumes in a pool:1. In the User interface, find the project, which you want to move.




110

3. In the Volume drop-down box, select the volume, on which to move the project.

4. Click Save.

1

indexIndex

Aaccess

the administrative interface 11the user interface 70the user interface from Linux 71the user interface from Mac OS X 71the user interface from Windows 71

activateProject Store 7

activity logview 67

adddescription to a project 38

administrative interfaceaccess 11

assignrole to a Project Store user 29

Cchange

project quota 47close

project 90create

new empty project 78new project from template 80project as administrator 31Project Store user 21Project Store user group 22

Ddatabase

reset 64delete

all proxies 58project 37, 91Project Store user 28Project Store user group 29proxies of selected project 59

descriptionedit 97

disableproxies 56security 18support for Project Store 13

downloadprojects list as .csv file 66

Eedit

project description 38, 97project keywords 99project type 100

enableproxies 55security 18support for Project Store 13

environmentset 15

exportproject 49, 86

Fforce close 52

project 90

Ggroup

Index

2

create 22

Hhide

Project Store volumes 14

Iimport

project 83install

Project Store 6

Kkeywords

add or edit 40edit 99

Llock

project 51, 89log out

the user interface 72

Mmodify

Project Store user 24Project Store user group 26

mountproject exclusively 88project for editing 88project for viewing 86

mount pointset for a project 45set preferred 107

moveproject between shares 50, 109

Ppassword

reset your own 74pause

proxies’ generation 58permissions

set 42, 104preserve

project mount state on client 17

previewgeneral project information 93project settings and contents 93project without mounting 91

project 52add description 38add keywords 40change quota 47close 90create as administrator 31create new empty 78create new from template 80delete 37, 91delete proxies 59edit description 38, 97edit keywords 40, 99edit type 100export 49, 86force close 52, 90import 83lock 51, 89mount exclusively 88mount for editing 88mount for viewing 86move between network shares 50move between shares 109preserve mount state on client 17preview general information 93preview settings and contents 93preview without mounting 91remove quota 47rename 36, 96rescan 65set as template 61, 102set permissions 42, 104set preferred mount point 45, 107set quota 47

project quotadisable 16enable 16

Project Storeactivate 7deployment environment 15disable support 13enable support 13install 6legacy projects 8reset database 64

Index

3

system requirements 6uninstall 8upgrade 7view activity log 67

Project Store SEfeatures comparison 4

Project Store userassign role 29create 21delete 28modify 24

Project Store user groupcreate 22delete 29modify 26

projectsdownload list as .csv file 66

projects depotimport project 83search 74

proxiesdelete all 58delete for selected project 59disable 56enable 55pause generation 58resume generation 58view generation progress 56

Rremove

project quota 47rename

project 36, 96rescan

project 65reset

projects’ database 64your own password 74

resumeproxies’ generation 58

Ssearch

the projects depot 74security

disable 18

enable 18set

deployment environment 15preferred mount point of a project 45, 107project as template 61, 102project permissions 42, 104project quota 47

system requirements 6

Ttemplate

set 61, 102

Uunhide

Project Store volumes 14uninstall

Project Store 8upgrade

Project Store 7set legacy projects 8

user interfaceaccess 70access from Linux 71access from Mac OS X 71access from Windows 71log out 72overview 72

Vview

activity log 67proxies’ generation progress 56

volumeshide 14unhide 14

Index

4

Documents

Project Stor 攀 ㌀⸀㜀⸀㈀ 唀猀攀爠ᤀ猀 േuide - Tiger Technology · 2020. 6. 27. · 28 Feb. 2017 Downloading the Projects List as a .csv File functionality added. 65

Project Stor 攀㌀⸀㜀⸀㈀唀猀攀爠ᤀ猀 േuide - Tiger Technology · 2020. 6. 27. · 28 Feb. 2017 Downloading the Projects List as a .csv File functionality added. 65