Replication and synchronization is a CaseMap feature that permits case staff to work in different local copies of a master case (local or SQL) that can be merged to create one updated version of the master case. You can create replicas of local and SQL cases in CaseMap.
Replication vs. Synchronization:
| • | Replication is creating an exact copy of a case while tracking the replicated file |
| • | Synchronization is merging the replica to the master case, reconciling any updates or edits |
When case users go on the road, they can take a replica copy along and make additions and updates to the case records. While these individuals work in replicas, case staff back in the office can still make changes to the master case. When a replica is returned to the office, it needs to be synchronized with the master case, merging changes made in the replica with those made in the master. CaseMap helps you reconcile any field update conflicts between the two cases.
|
Create replica cases for staff who need to work from home or access a case during court or offsite depositions.
|
|
For information on how to create a SQL case replicas in the CaseMap Admin Console, refer to CaseMap Server documentation.
|
Replication and synchronization involves:
| • | Creating a replica of the case |
| • | Working in the replica while others work in the master case or other replicas |
| • | Synchronizing the replica with the master case |
| • | Resolving any conflicts that occur between the replica and master case |
A CaseMap wizard helps you resolve conflicts between data updates in the replica and master cases. The wizard presents you with the data conflict and makes it easy to select which update to keep. During the synchronization process, you may also choose to postpone conflict resolutions to a later time when you perhaps have input as to which change should override an entry. You can make as many replicas of a case as needed and synchronize each file in any order. Replicas can only be synchronized with the master case once, and must be done one at a time.
A data conflict occurs when contradictory changes are made in the master version and in the replica. For example, one person working the master case edits the date of a fact, making it 3/1/99. Another person working in a replica edits the data of the same fact, making it 3/2/99. When the replica and master are synchronized, CaseMap recognizes that there is a conflict between these two data changes.
CaseMap analyzes conflicts at the field level within each record. In other words, if someone changes the date of the fact in the master case and another user changes the Evaluation field status for that same fact, no conflict occurs. Likewise, if someone changes the date of the fact in the master case and another user changes the date of the fact in the replica to the same date, no conflict occurs.
|
|
Reference the following table for guidelines and considerations when replicating and synchronizing cases.
|
Reference the following table for specific rules for users of both the replica and master cases, while a replica copy is checked out. The term "pre-existing" has the following meanings for the replica and master columns in the table below.
| • | Master — Pre-existing: A record or value that exists in one or more replicas that has not been synchronized. |
| • | Replica — Pre-existing: A record or value that exists in the master copy of a case. |
|
