Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Notes Replication Save Conflict Resolution/Archive Tool

IP.com Disclosure Number: IPCOM000014650D
Original Publication Date: 2002-Oct-29
Included in the Prior Art Database: 2003-Jun-20
Document File: 1 page(s) / 38K

Publishing Venue

IBM

Abstract

Idea of disclosure Lotus Notes creates a Replication Save Conflict document if two users update and save a document and have both changed the same field. However, there is no indication to the user of what was changed. A manual comparison needs to be done by the users to determine which field is in conflict. The comparison of these conflict documents is cumbersome and a manual process. In addition to the normal save conflicts, there may be thousands of "False" conflicts. In order to manually resolve the real conflicts from these false conflicts would have caused a tremendous burden for the development and support teams for the application. The first part of the solution to the manual process of finding and fixing the conflicts was to automatically find the false conflicts and archive them to a database. The other part was to take the remaining conflicts in the database find the correspoding document in conflict and determine which fields were in conflict. A memo is then sent to the users who caused the conflict detailing the fields that are different within the document and its conflict. This assists the user in resolving the conflict as it pinpoints the areas of the document that are in conflict automatically. The conflict document is then archived automatically. If the users determine that the remaining document contains the most recent information, no further action is necessary by the user. This memo states that if the data in the remaining document is not correct, that they must update it with the most recent information contained within the memo. One added advantage to this is that the conflict was archived and can be retrieved from the archive if necessary. This removes the burden from the user or support personell to resolve the conflicts due to the shear numer of them within the RMT application. 1

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 79% of the total text.

Page 1 of 1

Notes Replication Save Conflict Resolution/Archive Tool

Idea of disclosure

Lotus Notes creates a Replication Save Conflict document if two users update and save a document and have both changed the same field. However, there is no indication to the user of what was changed. A manual comparison needs to be done by the users to determine which field is in conflict. The comparison of these conflict documents is cumbersome and a manual process. In addition to the normal save conflicts, there may be thousands of "False" conflicts. In order to manually resolve the real conflicts from these false conflicts would have caused a tremendous burden for the development and support teams for the application.

The first part of the solution to the manual process of finding and fixing the conflicts was to automatically find the false conflicts and archive them to a database. The other part was to take the remaining conflicts in the database find the correspoding document in conflict and determine which fields were in conflict. A memo is then sent to the users who caused the conflict detailing the fields that are different within the document and its conflict. This assists the user in resolving the conflict as it pinpoints the areas of the document that are in conflict automatically. The conflict document is then archived automatically. If the users determine that the remaining document contains the most recent information, no further action is necessary by the user. This memo sta...