Consistent Version Numbering

[cprettyman]

At the moment, one consultant might save their model many times, publish it a few times, package and share it even fewer, and then another consultant consumes only some of the packages. So, the working model is (for example) version 20, but the shared version of the same iteration is version 10, and two different consultants who consumed it, would see it as versions 9 and 3 - but 2, 10, 9 and 3 are all the same iteration of the model, just seen in different contexts.  

Please either add another parameter, or modify how version is treated, so that there is an easy way to see that the version I consumed, and the version another consultant consumed are the same (or not) and that both are the same (or not) as the authors most recent published version.   Basically, let the model keep its version number as it is published, packaged and shared.

[Chad-Smith]

I'm not in favour of modifying how versions work, simply due to the fact that this would break how regular documents are versioned.

e.g. What happens when a Word doc is manually copied from one folder to another, or what happens if you upload a document with the same name but into another folder?

The Version is the record of how many times that document has been changed, and it should remain that way.

However, I'm not opposed to a new field/feature that maintains a reference to its previous versioned source.

e.g. In the case of Design Collaboration, a document-level metadata reference from Consumed > Shared > WIP.

But none of this solves the biggest underlying problem with the way that Design Collaboration and Docs works.

The fact that there are three instances of the same model in three different folders is the problem. Same for drawings.

And that a model/drawing isn't defined as a single instance with versions issued to recipients is the problem.

Docs (ACC/B360) - Change from folder storage/structure to metadata storage/structure