I am using OpenKM as a repository of web page components (images, templates, js and css files, pdf files, etc.). I am writing an application that uses OpenKM\'s SOAP API to pull specific versions of items out of the repository and push them to our content delivery network. (I\'m not serving assets from OpenKM, just populating the actual content server with items managed and stored in OpenKM.)
One thing that I have discovered that I need is an unchanging ID for any given piece of content, one that remains constant despite changes in the item\'s name or its location. Right now the closest thing to a unique key for a piece of content in the repository is path and name, and both of them are mutable, which breaks the link between an object in the repository and on the content server.
In the Jackrabbit repository behind OpenKM, I believe that need is fulfilled by the jcr:uuid property. However, that property is not exposed to the Document object in the SOAP API or, from my searching the source code for OpenKM, the Document bean.
What I would like to see is jcr:uuid exposed in the Document object as a read-only property, returned in the getProperties() method of the SOAP API.
Then I would always be able to find a document by using the search API\'s findByStatement() with the following kind of query (which I\'ve tested successfully):
//element(*, okm:document)[@jcr:uuid = \'64d68ec3-b12b-4f01-9af3-71568af9aedd\']
Any chance we can see this in an upcoming release?
Thanks,
MSM
One thing that I have discovered that I need is an unchanging ID for any given piece of content, one that remains constant despite changes in the item\'s name or its location. Right now the closest thing to a unique key for a piece of content in the repository is path and name, and both of them are mutable, which breaks the link between an object in the repository and on the content server.
In the Jackrabbit repository behind OpenKM, I believe that need is fulfilled by the jcr:uuid property. However, that property is not exposed to the Document object in the SOAP API or, from my searching the source code for OpenKM, the Document bean.
What I would like to see is jcr:uuid exposed in the Document object as a read-only property, returned in the getProperties() method of the SOAP API.
Then I would always be able to find a document by using the search API\'s findByStatement() with the following kind of query (which I\'ve tested successfully):
//element(*, okm:document)[@jcr:uuid = \'64d68ec3-b12b-4f01-9af3-71568af9aedd\']
Any chance we can see this in an upcoming release?
Thanks,
MSM