[OASIS Issue Tracker] Commented: (CMIS-727) AddbulkUpdateProperties operation

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/CMIS-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27007#action_27007 ] 

Jay Brown commented on CMIS-727:
--------------------------------

I was thinking about this after the meeting; and now I'm seeing where Florian was coming from. Aligning this method with something that would match a future (single) batch interface would be quite difficult and would make this operation much more complex than it currently has been proposed.      This has also led to me to think that when we do finally get around to defining batch operations we are more likely to have a small suite of them that looks something like:

   batchUpdate( parameters that make sense for update)
   batchDelete ( ... for  delete) 
   batchCreate( ... for create)
   batch<other verb here> ( ... )

[as opposed to the  single monolithic batch method that I was initially envisioning that handles all batch ops. One where the operation/verb (update, delete, create, etc) would an additional enum parameter. ]

In light of this,  I retract my comment about my concern of having a vestigial batch method in 2.0.   Rather (1.1's) batchUpdate (should we decide to have one) can be joined by 3 or more new (2.0) siblings that look as if they were designed to be a set.  All that would be required was that we decide on the naming convention for our 2.0 batch ops and use that now for update.

> Add bulkUpdateProperties operation
> ----------------------------------
>
>                 Key: CMIS-727
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-727
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Improvement
>          Components: Domain Model
>    Affects Versions: V1.1
>            Reporter: Florian Müller
>
> I would like to propose a new operation "bulkUpdateProperties" for CMIS 1.1 (see Proposal).
> Apart from other use cases, it would enable clients to change retention information and holds for multiple objects with one operation call.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira