topic Re: Multiple parents for document and deletion trouble- addchild in Alfresco Archive

Multiple parents for document and deletion trouble- addchild

annakan — Thu, 10 Mar 2011 15:58:21 GMT

Hello all.We need to be able to have a document inside two folders (one as work-flow basis, the other as filing/"storage").Looking around the forum (http://forums1.man.alfresco.com/en/viewtopic.php?f=6&t=16170) and doc we built an action that take the target folder (where the "duplicate" should

Re: Multiple parents for document and deletion trouble- addchild

annakan — Mon, 21 Mar 2011 15:02:21 GMT

Nobody has a clue ?

We are evaluating Alfresco on a small scale project and this is vital to avoid the messy workflows that would prove to be too constraining anyway.

Plus it is a great functionality for people workflows or not, it allows the same document to be filled under two logics, corresponding to different usages ('sorting plan' on one side, working reviews on the other side) that often conflict in a document lifecycle.

Last it allows very graphical / CIFS like process that are easier for occasional users who can even be un aware there is a DM in place.

We have a short time frame to complete this proof of concept, and it would be a big plus for Alfresco to be able to do something useful in this time frame, and it is quite frustrating to have the whole action stuff nearly working, but not quite …
Far away, so close

So any pointers appreciated

Re: Multiple parents for document and deletion trouble- addchild

lotharmärkle — Mon, 21 Mar 2011 21:06:19 GMT

I am not sure what you really meant by "doing the right behaviour" and what you want to achieve. Maybe you could just be more clear about this? Do you want the archive:// Noderef to be removed or do you want to remove a document which you linked in two spaces individually or …

There can be only exactly one primary association to a parent node.
This primary assoc controls the "contains" behaviour - that is, the life cycle of a node is controlled by its primary parent node. In other words, deleting a node will delete all its "primary" children as well. In contrast, all children of the deleted node, which have secondary assocs to it will not be deleted.

The mysterious archive://… node reference you see belongs to a node of the trashbin - it was deleted and the secondary assoc was changed to point now to the document located in the trashbin. If you empty the trashbin this will be removed too. So its not some kind of proxy or leftovers, its just a node reference.

HTH
lothar

Re: Multiple parents for document and deletion trouble- addchild

annakan — Fri, 01 Apr 2011 13:03:48 GMT

Thanks for your anwer I missed it because somehow I must have forgotten to activate notifications.

Thanks for your explanation, I less cleanly arrived to the same conclusion but was disappointed by some design decision :

- you must have one primary parent-child assoc, meaning you can't have "delete on last un-parenting" behavior.
- Or delete on "any" un-parenting behavior
- although afresco model supports multiple parents and this is GOOD and GREAT and much better in my book than the "proxy/stub" model, Alfresco forget that right away, implementing copy and move without passing the "source parent" information. The consequence is that the source is always fetched from the node itself, assuming it is its primary parent. That is wrong of course.

The consequence is that, when you assign multiple parents to a node/document, you can't act on any of the "non primary childs", all acts upon any of those is carried upon the arbitrarily elected "primary child" (the first parent at creation time in fact).

The moveTo and copy to signature are like this fn(node, destination), instead of fn(node, source, destination).

I was able to make work the multiple parenthood but I need to rewrite the copy and move action to be able to progress, something even more ambitious

On a side note they had to "do it right" for the CMIS implementation where a source and a destination are expected.

Re: Multiple parents for document and deletion trouble- addchild

mrogers — Fri, 01 Apr 2011 13:17:34 GMT

I think you may find that the copy scenario has been fixed … It looks like a familiar issue.

I like your idea of delete on last reference, but you are right that its not there at the moment.

Re: Multiple parents for document and deletion trouble- addchild

annakan — Fri, 01 Apr 2011 14:21:11 GMT

Great news

Fixed in the SVN ?

and the move action ? (greedy me)

To know if I still have to make my own (makeshift) custom move action.

As for the deletion policy, I happen to think that the "delete on last reference" is the most "sound" and generic but I would even be nice if we could choose the policy on a document type by document type basis.

More generally It would be nice if the move behaviour was preceded by onBeforeMove allowing us to mingle with the source and destination folder, thus implementing any policy.

As I said, greedy

Re: Multiple parents for document and deletion trouble- addchild

rss — Thu, 16 Jun 2011 08:42:27 GMT

We found the similar problem with Alfresco Share (r26807). (deleting and moving actions).

E.g.:
var folderNodeRef = "workspace://SpacesStore/e7bfa076-ab8a-4211-b821-e367ee36d33e"; //existing space "test"
var fileNodeRef = "workspace://SpacesStore/7831203d-805e-42d9-9a36-e4d1abbed1f0"; //existing document "file1"
var folderNode = search.findNode(folderNodeRef);
var fileNode = search.findNode(fileNodeRef);
folderNode.addNode(fileNode);
—-
Enter into space "test" and make action "delete". The document is really deleted and vanished from both primary and "test" spaces. But any trying to add a document with the same name "file1" into the primary space generates the following exception: "org.mozilla.javascript.WrappedException: Wrapped org.alfresco.service.cmr.repository.DuplicateChildNodeNameException: Duplicate child name not allowed: Файл1 (workspace://SpacesStore/Company Home/Data Dictionary/Web Scripts Extensions/………ourscript.post.json.hs#948"

We checked that the document is really deleted ( fileNode = search.findNode(fileNodeRef) returns null ), but folderNode.getChildren() for the primary space return Node-object with a name of the deleted document.

PS: the reason for using multiple parents for document for us is absence of virtual spaces. We need to process dynamic hierarchical lists of documents (working with clusters of documents) allowing all actions that possible in AlfrescoShare Document Library.

Moreover it is very strange that Alfresco Share contain different realizations for browsing documents in the library and viewing search results because it makes impossible to use actions for documents in search result that accessible for documents in the library.

Re: Multiple parents for document and deletion trouble- addchild

heiko_robert — Mon, 29 Apr 2013 12:54:32 GMT

moving a secondary is fixed now but I created a ticket in JIRA since deleting a secondary will still delete the primary node (tested in 4.2.c) ALF-18792.
The suggestion from Annakan would fix the issue