Our product stores (manages) its own documents in a content repository. Alfresco is one of the content repositories we integrate with, in addition to Documentum, Sharepoint, Oracle IPM, Hyland, etc.
We have our custom model for our documents. This custom model usually extends a type in the content repository. This custom model type will have its own set of (meta-data) properties.
In Alfresco, our model extends from cm:content. And we have our (meta-data) properties in an aspect. And our model type has this aspect as a mandatory one.
Past - Earlier work
Earlier we had Alfresco versions 5.0 and 5.1. In these versions, to create a custom model and package it to Alfresco Repo and Alfresco Share, I used the Jeff Potts notes [Working With Custom Content Types in Alfresco]. This article starts from 4 years old. With this, I created two AMP files: mymodel-repo.amp and mymodel-share.amp. Then, I copied these AMP files to folder: <ALFRESCO_HOME>/amps.
Then I ran the <ALFRESCO_HOME>/bin/apply_amps.bat to deploy this AMP into your Alfresco web application.
Now - Current
We are going with (or upgrading to) Alfresco version 5.2.
On top of this, I would be making some additions to our custom model (like adding two new properties).
I believe in version 5.2, I found that we can directly create/make the model from UI itself. This link [Content Modelling with Model Manager] has instructions to do this.
Though it does not matter now, I do not know if this model manager was available in versions earlier than 5.2.
Then I was not sure, if I can now create our custom model using this model manager UI, and then give the changes to (the repo and share) to our product clients to deploy (like we did through AMP packages).
With version 5.2, should or could I still use the AMP packaging method (the earlier way)?
I read here and there that there is a JAR way of packaging as opposed to AMP way of packaging. Is this applicable to this situation?
Or, in other words, in Alfresco version 5.2, what is the best approach to create and deploy custom model, along with its related share UI changes, to the clients of our product?
Could you please guide me?