Hello, currently I have an implementation which consists of a custom model of conList type (conList:letter). It mainly consists of the following properties:
I would like to change the model so it is a children of the folder type. So the new model would be folder:letter which would be applied directly to the folder containing the files using the following properties:
It would have a children type called folder:book with the following properties:
Also, I use the model customization so I can make cmis queries through some webscripts.
My question is: Is this good practice? Would I get a better result with smart folders templates? how would you implement it?
Hello,
I would suggest to create a content model just for the content.
Create a custom content type which would be the base of all your subtypes e.g. doc:BaseDocType.
All other subtypes like book, letter etc... should inherit the doc:BaseDocType.
There should be minimum properties under the doc:BaseDocType e.g. dococument_ID, dococument_Type etc...
For all other properties create aspects and attach them with the document types wherever needed.
This heirarchy is easily scalable.
Please let me know if you have further qeustions.
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.