For an introduction to Curator and starting the service see the article on Curator Configuration for Zoom versions till 7.2 and Curator Configuration for Zoom 7.3 onwards. This article discusses the initial setup, and, the process for subsequent configuration of the Curator service when Zoom HADR is being used. Zoom HADR provides High-Availability and Disaster […]
Setup of Curator with HADR Read More »
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 »
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 »
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 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 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.
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 »
In Zoom 6.0, the Web Management Console has a Curator Manager tab which shows some key information pertaining to the indexing engine Curator. It shows details of all the failed index calls in Curator server. This portion is not working on Zoom Windows server. Here is how you can fix it: Download the file from
Why Is The Curator Manager Tab Not Working In Zoom Server For Windows? Read More »
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 »
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,
Curator Dashboard Minimum Zoom version supported: 6.0 To launch go to System – Curator – Curator Dashboard List of Failed documents and Reindex failed documents Reindex All: An attempt is made to reindex all failed Assets Reindex Selected Assets: An attempt is made to reindex selected Assets Refresh: Fetch latest changes from Server From Zoom 7.3
How to check assets which failed to index Read More »
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 »
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 »
Introduction When a video file is checked into Zoom, every time a thumbnail of the video file is generated. The thumbnail is the first frame of the video. Prior to Zoom 6.0, the default frame was not configurable and always the first frame was treated as the thumbnail. From Zoom 6.0 and above, the user has
Configurable default thumbnail frame for video files Read More »
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 »
From Zoom 6.0 and above, Zoom supports configuring hot folders on remote machines directly from the Zoom Web Management Console. This is useful, for example, when we have to set up Hot Folders to run on headless terminals. Only superadmin users can perform remote Hot Folder configurations. Zoom Client Proxy service must be running on
Configuring hot folders from Zoom Web Management Console Read More »
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 »
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 »
Zoom 6.0, and above, supports customization of user-interface messages and text. If you are unsatisfied with the language of any particular installed message or text, you can make it more refined, easy to understand, or, relevant to your organization. This customization is meant to be performed by advanced users or system administrators. These custom messages
Customizing user interface messages and text Read More »
Problem In Zoom 6.0, On Mac client, we have seen that the default thumbnail applied to a video file at the time of import is not getting applied to the frame which the user has specified in percentage but the first frame is applied by default. Solution Download the latest ffmpeg distribution from the site: https://ffmpeg.org/
Configurable thumbnail percentage selection not working in Mac OS Read More »
