What is the difference between merged revisions and superseded revisions?

When you make two or more project copies from a master document, only one of them may be released as the new master document revision. The first one to be released wins. But what about the changes made in the other project copies?

Meridian provides three ways to resolve the remaining project copies made from the same master document:

• Discard the project copy. This assumes that because of whatever changes were made to the master document, the project copy is now obsolete and the project copy should be destroyed.
• Confirm Superseded by Master. This assumes that because of whatever changes were made to the master document, the project copy is no longer needed. In this situation, the system retains the project copy and its reference to the master document for future reference, but makes the project copy obsolete. The system also prevents the project copy from being released as a new master document revision.
• Confirm Merged with Master. This assumes that the changes made to the master document have also been made to the project copy. This option should be used after you have physically merged changes in the master document with the project copy. In this situation, the system retains the project copy and its reference to the master document for future reference. The system will allow the project copy to be released as a new master document revision (possibly after additional changes are made to the project copy) after which the project copy becomes inactive.

For more information about these options, see Reconciling with an updated master document.