[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=26862#action_26862 ] 

Florian Müller commented on CMIS-727:
-------------------------------------

Wait! I didn't want to kick off a general bulk operation discussion. That would be far too big for CMIS 1.1.

And, actually, I wouldn't want generic bulk operations at all. I would rather prefer something like stored procedures. (Maybe even without the "stored" part.)

Creating a folder hierarchy, for example, doesn't work as a bulk operation because you can't guess the intermediated folder ids in advance.  But it works as a simple script running on the server.

A script can also create, update, delete, version, etc. objects based on the state of other objects. For example, create a document with the attached content if it doesn't exist. If it exists, add a new version. One round-trip instead of potentially three. 

It would simplify transaction handling and error handling. For example, roll everything back if this exception is caught and delete just this last object if the other exception is caught.

It also would allow optimizing the data sent to and received from the repository. For example, run a query, gather some statics and only return a handful of numbers.

But that's CMIS 2.0 or even a separate specification. bulkUpdateProperties was only meant to close a gap for 1.1. 


> 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