Administration

Create A Custom Media Converter For CR2 Files

The necessary files for this process are available from the Evolphin Support team upon request. The following steps should be run by the evolphin user. Download the files cr2-converter.xml and cr2-converter.tar.bz2 Extract cr2-converter.tar.bz2 to /home/evolphin/zoom-deploy/ Open Terminal and run the following command under this directory: chmod +x cr2-preview-extractor.sh Test the converter by running an instance of the

Create A Custom Media Converter For CR2 Files Read More »

Setting default umask/File Permissions for Zoom/Preview/Solr Servers

It is possible to set default umask for the files and directories created by Zoom products like Zoom server, Preview Server, Solr Server and HADR File Transfer Server.  Setting the default umask for Preview Server Preview server generates the previews of ingested assets on Zoom server. All the generated previews are stored in preview server cache. By

Setting default umask/File Permissions for Zoom/Preview/Solr Servers Read More »

Vantage Media Converter

With Zoom 5.8 and above, Vantage can be used to generate previews of video files using Zoom media converter. What you need to start: Working Zoom and Preview Server. Running Vantage Node. Zoom should be installed on the machine where vantage scripts needs to be executed. A shared location between Vantage node and Preview server. This

Vantage Media Converter Read More »

Zoom Indexer

Zoom has an extensible framework using which it is possible to augment the off-the-shelf functionalities provided. One such enhancement is the ability to define a class of assets that physically reside outside of the Zoom system, but still can be referenced from within Zoom by means of association with proxies. The Indexer suite of scripts provide

Zoom Indexer Read More »

Re-Indexer

Zoom Indexer provides a way of maintaining assets outside the Zoom repository, while still being able to reference them using proxies. (Refer to setup details here). For a growing set of assets present in a source location, we may want to continue indexing newly added assets periodically even after the completion of the initial indexing.

Re-Indexer Read More »

Restricting Project Size

Zoom 6.0 and above supports adding a restriction on project size and number of files it can have. Feature highlights: Impose max size quota on a project.  Impose max files count on a project. Once any of the above limits reached, the project won’t grow further either in terms of size or number of files. Please follow

Restricting Project Size Read More »

Indexes on Curator

Indexed Doc An indexed doc means Asset on that revision has been successfully added to Curator. You can check whether a document is indexed in Asset Browser. Go to Actions – Index Status The above image has following details for Asset ID 832   At Repository Revision (RRN) 102 Non-Content status is INDEXED Content status is

Indexes on Curator Read More »

Resetting Curator

Clean State of the Curator Stop Curator Service You have to delete the Curator indexes: For Zoom 7.2 and below, locate the directory specified in  <ZOOM_INSTALL_DIR>/conf/server.xml under the tag <solrDataDir> inside <FtsSpec>. Delete this directory from disk. In the FTS Spec specified here, the directory path mentioned in the tag <solrDataDir> is /opt/zoom/db/solr-db/ For Zoom 7.3 onwards,

Resetting Curator Read More »

Advanced Curator Configuration with XML Specification

Minimum Zoom version supported: 6.0 Not valid from Zoom 7.3 onwards. This document describes the various configuration parameters of Curator. Basic Configuration The basic configuration that must be performed involves the following aspects. The associated config fields are also given for each step. Enable or disable file content indexing. Config field: fileContentIndex Enable or disable

Advanced Curator Configuration with XML Specification Read More »

Curator Backup and Restore

Minimum Zoom version supported: 6.0 Curator backup and restore can be performed either through a web API or manually. Both methods are described below. Backup Web API Stop all Zoom Servers. Open the following URLs in the order they are written http://<curator-server-hostname>:8983/solr/BK/replication?command=backup http://<curator-server-hostname>:8983/solr/ID/replication?command=backup Start all Zoom Servers Backup Name: You can give a name to

Curator Backup and Restore Read More »

Logs Management in Zoom

In Zoom 6.0 and above, the various logs related to zoom, curator and preview servers will be available in a tab named “Log Browser” in Log Management tab of Webmin and Log Management Tab of Z-Settings dialog. Zoom Server-Side Log Management : Panel Components : Select Logs Files Section: Drop-down menu options for selection of logs files are

Logs Management in Zoom Read More »

Additional Preview Cleanup Options

  As of Zoom 6.0, new options have been added to preview server cleanup settings. DO_NOT_CLEAN_FUIDS: This option will skip the original asset source file from the cleanup. In other words, original asset file will not be deleted by cleanup process. DO_NOT_CLEAN_PREVIEWS: Do not delete any preview file. Generated previews will never be deleted. DEFAULT: the Cleanup process will decide based on

Additional Preview Cleanup Options Read More »

Metadata Editor in Zoom Server

From Zoom 6.0 onwards, Zoom administrators can edit the system-wide metadata schema from within the Web Management console’s Metadata Editor page. Open the Metadata Editor page under the System node in the Admin Menu sidebar. The metadata schema is saved in the metadataspec.xml present in your Zoom installation’s conf/ folder.   The page has three

Metadata Editor in Zoom Server Read More »