Configuring drag-and-drop functionality from the Elvis 4 Desktop client to other desktop applications
Note: With the discontinuation of support for Adobe Drive, the Elvis Drive has been made obsolete.
Without further configuration you can start using the desktop client to import or download content. To be able to directly drag-and-drop items from the client into other desktop applications, these applications need read-only access to the original files on the Elvis server. Essentially the desktop client drags the path (a link) to the original file to another application. Depending on how and where you drop the item it may be copied to your desktop, linked to from Adobe InDesign or opened in Adobe Photoshop.
Create file share on server
- Create a read-only network file share with the name elvisFilestore
- The share should point to the Elvis mainFilestore in the Elvis Data directory, for example:
C:\Elvis Data\mainFilestore (Windows)
/Library/Elvis Server/data/mainFilestore (Mac OS X)
Note: Make sure this share is read-only, otherwise the index may become out-of-sync with the content stored on the file system.
- Open the Elvis server configuration
- Define the share path as UNC path in the dragFromReadOnlyShare variable in the config.properties.txt file. When set, this path will overrule dragging to reference the file from a read-only UNC share instead of dragging the file from a connected Elvis Drive.
- Save all changes and restart the server
Enabling share access on Windows client machines
To enable drag-and-drop from the desktop client on Windows, make sure the Windows or ActiveDirectory user has sufficient permissions to access the file server and the elvisFilestore share you just created.
The desktop client will drag an UNC path to the asset as configured in the dragFromReadOnlyShare in the Elvis server configuration.
Enabling share access on Mac OS X client machines
To enable drag-and-drop from the desktop client under Mac OS X you have to mount the share with its complete path:
Make sure you include the share name. The desktop client will drag an UNC path to the asset mapped to /Volumes/elvisFilestore. When you mount the share by just typing the servername and then selecting the share, Mac OS X will mount it as /Volumes/ServerName causing the mapping to fail.
Using Mac OS X workgroup server you can configure the share to be mounted automatically when users log in.
Enabling share access on a Mac OS X demo laptop
A share to the Elvis main filestore must be configured to enable read-only access from Elvis clients to the Elvis server, allowing users to drag and drop files onto the desktop or into an application. The default way to configure this, is to create a new shared folder on the server and add the share path to dragFromReadOnlyShare property in the config.properties.txt file. The Elvis client user can mount the share and perform the drag operations.
There is a problem when the Elvis client and server are running on the same Mac OS X machine (for example in a demo environment). It is not possible to mount a local file share in Mac OS X. A solution to overcome this issue, is to create a symbolic link to the main filestore and use this as a "fake" share in the Elvis configuration.
To configure this:
- Open the Mac OS X terminal.
- To create a symbolic link to the main filestore, verify that the path to the mainFilestore location is correct and run the following:
$ ln -s /Library/Elvis\ Server/Elvis\ Data/mainFilestore /Volumes/ElvisFilestore
- Open config.properties.txt in your Elvis server configuration.
- Edit the dragFromReadOnlyShare property to dragFromReadOnlyShare=\\\\127.0.0.1\\ElvisFilestore
- Save the file and restart the server.