Re: [cmis] thinClientURI discussion

["Huebel, Jens" <j.huebel@sap.com>]

Hi Jay,

first I felt exactly like you: who should use this? But the more discussion we had the more I felt unsure about my first impression. While I am not (yet) convinced that it makes sense to have this on every object, it could be useful on documents, items and folders .

I have seen frequently scenarios where you extract data from a leading system along with some kind of attachments. These may be financial records, employee files, invoices, contracts or whatever. Often you build ECM applications presenting these things in a quick and user-friendly way. Some users however want to have a link back to the originating system. For example if they want to change a record. The proposed enhancement would provide a mechanism to do such things in a standardised way. IMHO it would be useful that a generic CMIS client could provide such a functionality working for any repository. Could you imagine to have something like this in your Content Navigator application?

I feel this needs more discussion but perhaps we rejected it a bit too fast.

Jens

From: Jay Brown <jay.brown@us.ibm.com>
Date: Wednesday 29 January 2014 00:19
To: "Mueller, Florian" <florian.mueller02@sap.com>
Cc: "cmis@lists.oasis-open.org" <cmis@lists.oasis-open.org>
Subject: Re: [cmis] thinClientURI discussion

I agree this would be a clean way to do it, but I don't have a use case for this here.  

Perhaps someone else will...


Jay Brown
Senior Engineer, ECM Development
IBM Software Group
jay.brown@us.ibm.com

"Mr. Florian Mueller" ---01/28/2014 09:18:54 AM---Hi, In our last call we discussed (and finally rejected) the idea of a thinClientURI that can direct

From:	"Mr. Florian Mueller" <florian.mueller02@sap.com>
To:	cmis@lists.oasis-open.org,
Date:	01/28/2014 09:18 AM
Subject:	[cmis] thinClientURI discussion
Sent by:	<cmis@lists.oasis-open.org>

---

Hi,

In our last call we discussed (and finally rejected) the idea of a thinClientURI that can directly access the native repository web interface for folders and documents.
Today, I had an idea how this could be done in a very lightweight fashion with (and only) the browser binding.

Browser binding object URLs have a cmisselector parameter. We could introduce a new value for that, for example „native“. It either returns the HTTP status code 307 (Temporary Redirect) with a Location header pointing to the native web interface for this object or the HTTP status code 404 (Not Found) if the repository doesn’t have a web interface or doesn’t want to provide this feature. How the redirect URL is composed is repository specific and could depend, for example, on the object type and on the property values of the object.

Do you think this idea is worth pursuing?


Regards,

Florian