Custom properties using DotCmis

[anca.antonie]

I have installed OpenKM server and I am using DotCMIS library for documents upload/download, which it works nice(I succeeded in making this work). But I am trying to set custom properties on documents. I have created groups and set properties such as:

Code: Select all

Dictionary<string, object> properties = new Dictionary<string, object>();
properties[PropertyIds.Name] = documentName;
properties[PropertyIds.ObjectTypeId] = "cmis:document";
properties[PropertyIds.ContentStreamId] = 1;
properties["okp:contract.cups"] = "property_name";

contentStream.Stream = myStream;

IDocument doc = resourceFolder.CreateDocument(properties, contentStream, null);

and I receive the error: Property +'okp:contract.cups' is not valid for this type!

I saw an example with Alfresco custom properties, but I can make this with OpenKM and DotCMIS??

[RomanA]

Are there any news on this issue? I'm struggling with the same problem, I need to add custom metadata to my documents, but find no way to do this through CMIS. Is there no way at all? I already took a look at how a document object looks like that was fetched from a server and already had a custom property group assigned to it, but I cant find any trace whatsoever of those custom properties.
Any help would be greatly appreciated.

[pavila]

I think this feature is not implemented. If anyone send me a patch with this improvement, I'll add to the source code.

Regards.

[fabiobenedetti]

Hi to all,
i'm having the same issue uploading content from a scan software that support cmis.
I can't upload "okp:property_name" and can't read any of this property using cmis workbench
I added properties in openkm "metadata group" section.

There is a solution for this at now??

[jllort]

Is not implemented. My personal suggestion is not using CMIS. Particularly I'm not a "fan" of this API. In the past, we were excited about it, but when we played in deep with it we observed some mess. Basically, In my opinion I think the persons - DMS software - involved in this API introduced a lot of things what goes right in their product scenario but what in other does not have a sense ( for example, folder versioning is something quite strange in almost DMS ).

My suggestion is to use our REST API ( ours or if you decide to go with other DMS theirs ). Usually CMIS is sold as portability etc..., if in future you migrate to another DMS the connection to your current application will still working etc... sound fine, but sincerely if in future you migrate between DMS your problem is not the API, your problem is how to migrate data ( and CMIS is not the right way for doing it ).

[fabiobenedetti]

Thank's for your reply;
it's just because my scan software use cmis to upload properties to dms.
Maybe it's time to learn how to use the Rest api.
Many thanks again.

[fabiobenedetti]

Googling i'll find this: https://docs.openkm.com/kcenter/view/imp-station/
This can help me to easily import files generated by Chronoscan but i don't understand if it will become available for Community edition.

[jllort]

This feature currently only is working for professional edition. However you can create and small java application to upload using the SDK for JAVA or .NET ( it is quite easy ).
Take a look at ( in this order ):
https://docs.openkm.com/kcenter/view/sd ... lient.html
https://docs.openkm.com/kcenter/view/sd ... mentSimple
https://docs.openkm.com/kcenter/view/sd ... tiesSimple