Model Organisation - best practice?

[Matt Thomas]

Hello There

I’ve run into some trouble with a large project containing several models. One model is a “common” model for document templates, standard types, a library of actors, etc. Other models relate to different products within our organisation, so there are links between the elements in the “common” model and other models, and a some links between the different products too.

I’m using SQL backend and Subversion and it has all worked very well so far. I recently upgraded to 9 (build 905) and was lax in not checking everything in. After the upgrade there was a failure to checkin – problems with links between XML files. Doing a resync VC status, it appeared that the packages were committed. I then did a get all latest and the model reverted to an older state. I can recreate as I had generated documents that I can use to help.

My question is really about model organisation. Are there any white papers or other guidelines on structuring a large project with multiple models. I’m tempted to have a single model (and single VC model repository) so there are no links between elements of items in different VC model repositories. The idea is to prevent the model VC versions from getting out of sync.

In looking at this subject, I’ll also be interested in best practice / advice on structuring packages within models where the contents relate to different, but related products.


Very best regards

Matthew