File import filter....

Ben_inform

Hi,

At one of my client law firms on WS8.0 SP1 they have a DMS with caching architecture with the file store and SQL stored centrally.
This operates normally fine but if someone in say Perth connected to a Perth DMS w/ caching (with 60ms Latency to Sydney) UPLOADS a new 200Mb document into worksite, that document blocks the cache upload queue (which is FIFO) until it is sucked across the WAN to the central Fils store in sydney.

. This block of the cache upload queue can lead to collaboration issues e.g. the Secretary checks in a large document (when connect to perth DMS w/ caching) and tells Lawyer its checked it, but the lawyer wont see it checked in till the file has gone through the upload queue and been "centralised".


So, as a workaround, is there a way to block certain file types (e.g. PST files) or detect large file sizes at the client side?


I guess I could write a command wrapper around the import but there are so many other commands relating to doc import (e.g. drag and drop) to cover right ?

Any ideas on a general file import filter.....?


Thanks.....

DaleN

You could try using the FileSave.NRS and/or the NewProf.NRS scripts to capture when files are being added to the system. The GetDocumentTypeFromPath method can be used to check the file type (assuming there is a INSO Type mapping setup in the primary WorkSite library). You can also use File System Objects to information about files such as their size.

Problems would be that in some cases the path and filename information are not passed through in the ContextItems collection so you don't always have that information to work with. You'd also have to handle situations where users drag and drop into FileSite folders and they're using the auto-profile option so that no dialog comes up.

Good luck!