Bug #2360

Document Identifier Conflict Resolution

Added by Will Tyburczy over 16 years ago. Updated almost 13 years ago.

morpho - general
Target version:
Start date:
Due date:
% Done:


Estimated time:


Currently, Morpho uses the <scope> and <lastId> to generate the next document
id for any new document. When saving locally, if a document with this id already
exists, it will simply be overwritten silently. When saving to the network, the
save will generally fail silently. When there is a naming conflict like this,
the user should be alerted and given options for how to deal with the confict,
such as saving it with a higher revision number, saving it under a different
document id, etc.

Related issues

Has duplicate Morpho - Bug #3454: Fixing docid conflicts in metacat or local fileResolved07/16/2008

Blocked by Morpho - Bug #2285: Morpho creates a duplicate dp that has an existing docidResolved11/22/2005

Blocked by Morpho - Bug #2309: File name conflict resolution when using same scope on different computersResolved12/06/2005


#1 Updated by Callie Bowdish almost 14 years ago

My understanding is that previous versions of Morpho handle document conflicts. Judith worked with a previous version recently and didn't have the same problems as those working with the current version.

#2 Updated by Callie Bowdish almost 14 years ago

I tested previous version of Morpho 1.6.0 and found that it had problems with doc ids too.

#3 Updated by Jing Tao almost 14 years ago

it is duplicated to bug 3454

  • This bug has been marked as a duplicate of bug 3454 ***

#4 Updated by Jing Tao almost 13 years ago

move to 1.7

#5 Updated by Redmine Admin over 9 years ago

Original Bugzilla ID was 2360

Also available in: Atom PDF