Bug #417

Is sequential numbering of versions needed?

Added by Dan Higgins over 18 years ago. Updated over 18 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


Currently, version changes of documents must be sequentially numbered. This
means that someone working locally in Morpho might make 6 changes to a document
and 6 versions must be sent to Metacat in order, even though only the last one
is meant to be submitted. Also, if any of the early version is invalid then the
whole submission fails. Likewise, a download of any datapackage requires the
download of all version, even if only the most recent is needed.

Therefore, I suggest that submission of new versions only require that the new
version number be greater than the current one, not exactly one greater.


#1 Updated by Matt Jones over 18 years ago

I think I agree. This feature is somewhat left over from when metacat did the
sequence number assignments. I think we still need to be sure, however, that
the user has the most recent revision before allowing them to update. Basically,
if metacat has x.50.6 as the most recent revision, and the user tries to update
to x.50.7 or greater, then fine. But if they try to update to x.50.6 or less,
then it must be rejected still. This change will be backwards compatible with
morpho 1.0.0 so that will be ok.

#2 Updated by Jing Tao over 18 years ago

A method named getLastRevisionNumber was added to AccessionNumber class. And
condition for checking accession number was revised too.
Now metacat wouldn't refuse a revsion number which is 2 or more greater than
current revision number in the database.

A constructor was added to DBSAXHandler class. In this constructor, user can
specify the revision number he want to update. And the number can be passed
into a DocumentImpl object constructor in startElement method. But the
number should be greater than current number in database.

A constructor for DocumentImpl class was added. In the new constructor, user
can specify the revision number he want to update. In method
writeDocumentToDB, when a update action happend, the rev number would not
automatically to add one, but it can update to specified number.

#3 Updated by Redmine Admin over 7 years ago

Original Bugzilla ID was 417

Also available in: Atom PDF