I see what you are trying to do now. Instead of typing a property as a more
fundamental type, like d:text, you want to type it as a complex type, in your
case acme:userNote.
I believe this is possible, but I've never tried it or seen it done. You'll
have to do much more than declare it in your
Mark,
I haven't done this myself, but it should work by defining the property
as multi-valued, as done with the "multiple" setting in this example:
Tags
d:category
false
true
true
true
false
Karsten
Thanks for replying. The permission question is already being addressed by
the UI implementation so that is not an issue based on how this is being
done. Notes, once entered, are NOT going to be editable. They will only
be displayed as a "note history" - this List<>, attached to the do
Mark,
adding a multi-valued property for your UserNotes should be
straightforward by defining this in your model for Alfresco.
But be aware that the Alfresco permission model (like most other ECM
systems) only manages one permission per document object. You cannot
have different permissions
Jeff
I did read your updated version of the Alfresco Content Model paper
(SomeCo)
http://ecmarchitect.com/images/articles/alfresco-content/content-article-2ed.pdf.
I saw the model that you have for modeling the "whitepaper" concept. I
don't think anything short of being able to add a multi-value
Hi Jeff
Thanks for the quick response (seems to be common on this list which is
really appreciated).
I see what you are saying. Not sure if it is quite along the idea the team
was thinking of for this application. The notion of being able to
model a *UserNote
*object and hold a List<> of them a
Mark,
You could use relationships in repositories that support it to associate
documents with N notes. For repositories that don't support it, a note could be
a cmis:document and you could track cmis:objectId's of notes in a multi-value
property on the cmis:document (more likely a child type of
I have seen a few threads on a similar topic so pardon if this is
duplicated.
First off, I know that this is completely dependent on the ECM product
supporting this. 2 ECM products are being considered - SharePoint 2010 (or
possibly 2013) and Alfresco 4
Second this an all Java implementation fro
