Quick Upload is a tool to move files from client computers and network locations to the central OpenEngagement server, or to initialize the DMS by, when uploading files, also creating the site structure to be used by the DMS. That is, users may optionally use Quick Upload to create the initial collection of Areas, Entities and Sections within the site. Alternatively, firms may define their site structure using the web browser interface and may use Quick Upload simply to move files into the DMS and KMS.

Content may be moved to either the DMS or KMS. This will likely be done by each firm only one or two times, when first using OpenEngagement. Quick Upload, though, may also be used to send scanned images to the server as they are created, so some firms may continue to use Quick Upload for this purpose.

Quick Upload is installed generally on a subset of the computers where the Go-Between is installed. That is, it is not likely installed on the same computer where the server is installed, though on some networks this may be possible, and it is not likely installed on all computers where the Go-Between is installed. As it is used to move files from office computers and laptops to the server, it would usually be installed where the files are. However, using Quick Upload requires the use of user accounts with full or almost full access permissions to the DMS and KMS. Firms, therefore, may not wish to have every staff member using Quick Upload. Some firms may temporarily give most staff full access to the DMS and KMS, or may assign a certain set of users to perform the Quick Upload operations. The latter is generally the best option, as it ensures the files are uploaded in a consistent manner, with respect to where they are placed and what metadata is assigned.

Quick Upload will often take some time to run, particularly if there are hundreds or thousands of files to upload. In the case where there are many thousands of files, users may wish to leave the application running overnight, once the target locations and metadata have been specified for the files.

Quick Upload works by allowing users to specify which files are to be sent to the OpenEngagement server, their target location within the DMS and, optionally, what metadata is to be associated with each file in the CMS. Quick Upload will begin uploading files as soon as the target locations are set, even if the metadata has not yet been set. This allows it to work in the background while users continue to specify what it will upload, to where, and with what metadata.

Users may add files one at a time, may drag and drop multiple files into the interface, or may specify to upload entire folders using the Initialize Site feature.

When using Quick Upload, the first dialog that appears is the login dialog. This prompts the user for the server information (server name, port, and path) and their user information (user id and password). As using Quick Upload allows users to upload large volumes of content to any location in the site, only users with the Manager or Site Manager role site-wide may use Quick Upload.

Once this dialog is filled in, all values other than the password are saved, so that when using Quick Upload later, only the password will need to be filled in again.

Once logged in, Quick Upload will check the version of the Quick Upload and server are compatible. If they are not, likely the easiest solution will be to download another, more recent version of Quick Upload from the OpenEngagement web site.

Once logged in, users are presented with the main user interface, which consists primarily of a field listing each file the user has selected to upload and some information related to these files. Above this are the buttons related to the user actions: Init Site, Monitor, Add Files, Set Target, Set Metadata, Retry, Stop, Resume, Remove and Close. At the bottom is the progress summary information.

For each file, the user interface lists:

• Source - the location on the local drive/network of the file
• Target - the location within the DMS or KMS where the file will be sent
• Target Type - either Area, Entity, Section, Engagement, File, or Image
• Upload Progress - either Target Not Set, Period End Not Set, Pending, In Progress, Stopped, Failed or Completed
• Metadata Progress - either Target Not Set, Period End Not Set, Metadata Not Set, Pending, In Progress, Stopped, Failed or Completed
• Title
• Period End
• Description
• Keywords
• State/Visibility
• Local Roles

The last six columns are either blank or 'Set', indicating if each metadata field has been set for this file or not.  In most cases, the metadata may be left undefined, but this interface makes it easier to track what metadata has and has not been set.