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] Updated: (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:all-tabpanel ]

Gregory Melahn updated CMIS-764:
--------------------------------

    Proposal: 
Two new parameters, filterObjectTypeIds, filterBaseObjectTypeIds, will be added to the services getChildren and getDescendants.    

A client may use zero or one of the parameters on a service request.    If neither parameter is used, then the results will not be filtered by types (i.e. the services will behave as they do now).

Support by servers for the new parameters will be required.   



  was:There are several ways this could be done.  One way would be to add optional parameters to the getChildren and getDescendants services (filterObjectTypeIds, filterBaseObjectTypeIds) which would contain a list of typeId's, objects of which should be included in the result set.  Another approach would be to add optional new services (getFilteredChildren, getFilteredDescendants) that use those parameters.    There would also be a new capablity defined to indicate whether the repository supported this capability (capabilityFolderFiltering)


> 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]