CMIS - "Project" item has inappropriate properties

The CMIS Connector seems to think that the base type id of a Content Server Project item is cmis:document. The reported properties for a Project item I created in my test CS 10 server are listed below.

Is this a known issue?

Prop Name: 'Object Id' Id: 'cmis:objectId' QueryName 'cmis:objectId' Value: 'elpartition/50181'
Prop Name: 'Object Type Id' Id: 'cmis:objectTypeId' QueryName 'cmis:objectTypeId' Value: 'dm.Object'
Prop Name: 'Created By' Id: 'cmis:createdBy' QueryName 'cmis:createdBy' Value: 'dgamble@ott-dev-lab.opentext.net'
Prop Name: 'Created At' Id: 'cmis:creationDate' QueryName 'cmis:creationDate' Value: '2011-11-28 19:52:04'
Prop Name: 'Last Modified By' Id: 'cmis:lastModifiedBy' QueryName 'cmis:lastModifiedBy' Value: '<unknown>'
Prop Name: 'Display Name' Id: 'cmis:name' QueryName 'cmis:name' Value: 'ECCORE10.3'
Prop Name: 'Is Immutable' Id: 'cmis:isImmutable' QueryName 'cmis:isImmutable' Value: 'True'
Prop Name: 'Is Latest Version' Id: 'cmis:isLatestVersion' QueryName 'cmis:isLatestVersion' Value: 'True'
Prop Name: 'Is Major Version' Id: 'cmis:isMajorVersion' QueryName 'cmis:isMajorVersion' Value: 'True'
Prop Name: 'Version Label' Id: 'cmis:versionLabel' QueryName 'cmis:versionLabel' Value: '<not versioned>'
Prop Name: 'Version Series Is Checked Out' Id: 'cmis:isVersionSeriesCheckedOut' QueryName 'cmis:isVersionSeriesCheckedOut' Value: 'False'
Prop Name: 'Is Latest Major Version' Id: 'cmis:isLatestMajorVersion' QueryName 'cmis:isLatestMajorVersion' Value: 'True'
Prop Name: 'Version Series Id' Id: 'cmis:versionSeriesId' QueryName 'cmis:versionSeriesId' Value: 'elpartition/50181'
Prop Name: 'Last Modified At' Id: 'cmis:lastModificationDate' QueryName 'cmis:lastModificationDate' Value: '2011-11-28 19:52:04'
Prop Name: 'Base Type Id' Id: 'cmis:baseTypeId' QueryName 'cmis:baseTypeId' Value: 'cmis:document'

Find more posts tagged with

Comments

eLink User

Hi David,yes, this is a known issue.Content Server Projects are unsupported objects to CMIS since, similarly to other CS specific objects, they are exposed as dm.Object instances from the Enterprise Library / CS interface. The CMIS connector at this point is not able to distinguish what kind of instance this might be. However we decided to expose those objects anyway not to break the paging semantic on getChildren and getDescendants calls.Since CMIS doesn’t not define anything else other than “document”, “folder”, “relationship” and “policy”, we decided to expose those “unsupported” objects as a document with almost all Allowable Actions on false.Have you special requirements for those object types?Stefano

bsisko

Hi Stefano,

Ideally, I'd like to be able to treat Project and other special container types as folders so that their contents can be enumerated. In the meantime, I'll have to adjust my code so that it makes fewer assumptions about allowable actions for documents. Of course, that's not a bad thing anyway.

David