Introduction

A team work flow is a process that uses the IP-Protector software to move documents from many team members to a central archive. The IP-Protector software helps to automate this process and adds proof of the content by applying digital signatures and time stamps.

Team Member activity

A team member creates a weekly export using IP-Protector software. The exported zip file is stored to a network location.
Screen image

The zip file contains signed and time stamped copies of:

• New documents and data.
• Documents that were revised.

Note: The IPP application will warn the user about which documents have been revised or modified since their last signature.

Directory organization of central storage:

< network drive >	For example, a central computer that is mapped to "E" drive
< project folder >	A folder is named to indicate that this is work for review or counter signature.
"outbox"
< researcher name >	By person
FEB022002.zip	A set of documents exported

Reviewer activity

The process of "reviewing the work" results in a counter signature of the same documents. (description of a counter signature)

1. Screen image Use the Import page in IPP to preview the contents of the zip file.
2. Click on Counter Sign All in the preview mode
3. Step 3. Click on Save All of the counter signatures to the original zip file.

Screen image

Optionally, when previewing the zip file, the reviewer may store the documents in a directory that supports searching using this work flow:

Steps 1 and 2 are the same as above
Step 3. Click on Import All of the documents. The user is prompted for the directory where the documents are to be stored.
Step 4. The original ZIP file can be deleted.

Network Support activity

Backups are scheduled for documents in the central storage. If the reviewer uses the 'unpack and store the document' displayed option above then the reviewer's IPP database of signatures must be included in the backup.

Optionally, security should be set on directories to allow appropriate update access. The Team Member has read/write access to their individual "outbox" on the central storage location. The Reviewer has read/write access to all researcher folders in the central storage. If the reviewer uses the 'unpack and store the document' then the storage directory should be read-only for all persons except the reviewer that needs write access.