Document conversion and caching in Relativity Viewer

Document conversion and caching in Relativity Viewer

January 8, 2018

It's a good idea to have a basic understanding of how Relativity converts and caches images and native files so users can redact and mark them up.   If a document has already been converted, Relativity may be able to directly download the HTML version from a cache.    If not, a processing engine will convert documents to a format that a viewer can display when the user opens the document. 

 

 

The cache manager will not keep converted files indefinitely.    A single setting, 'FileDeletionManagerBatchAmount' controls how many documents this manager will delete in individual batches.  

 

Relativity users a 'zero footprint' viewer.  This means that on your network, there's no need for installations.   Documents and images are viewed directly in the web browser.   So for example something like a Word document will be loaded in a format that a browser can interpret.  Native applications will not be required for images, natives, or images that are saved as a PDF, but only if a native file is saved as a PDF

 

You may experience some trouble with keyboard shortcuts in Relativity that conflict with those used in a web browser.   Relativity does not have a way of resolving such conflicts. 

 

Note that Relativity recommends that admins change the default setting that has one worker handle conversion, processing and imaging if a workspace is expected to have more than 100 simultaneous users.   Instead one work should be dedicated to conversion. 

 

Please reload

Contact Me With Your Litigation Support Questions:

seankevinoshea@hotmail.com

  • Twitter Long Shadow

© 2015 by Sean O'Shea . Proudly created with Wix.com