OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

cmis message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (CMIS-764) Provide the ability to filter the results of getChildren and getDescendants by type

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

Jay Brown commented on CMIS-764:

How about overloading the same services we have now and specify that if these new filters are either null or not present  then the behavior should be to return all supported types.  (so inclusion of the filter in the call would be optional for the client)

As for being supported on the server side for v.next I would vote that this should be part of the required base (not optional) since there is no technical reason why a otherwise compliant repository could not accommodate this.  (Since worst case it could do so in an inefficient manner)

If there were issues with the client optional parameters then I would be in favor of the getFiltered... services but again I don't think they should be optional. 

> Provide the ability to filter the results of getChildren and getDescendants by type
> -----------------------------------------------------------------------------------
>                 Key: CMIS-764
>                 URL: http://tools.oasis-open.org/issues/browse/CMIS-764
>             Project: OASIS Content Management Interoperability Services (CMIS) TC
>          Issue Type: Improvement
>          Components: Domain Model
>            Reporter: Gregory Melahn
> It would be convenient for clients to be able to navigate the folder hierarchy, but filter the result sets to include selected types of fileable resources.   For example, a support engineer using a CRM app could select only to see files of type crm:log

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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]