[#CMIS-170] get folder by path - OASIS Technical Committees Issue Tracker

OASIS Content Management Interoperability Services (CMIS) TC

get folder by path

Created: 03/May/09 05:57 AM Updated: 11/Jan/10 06:54 PM

Component/s:

REST/AtomPub Binding

Affects Version/s:

Draft 0.61

Fix Version/s:

Draft 0.62

Proposal:

« Hide

add to domain, ws + rest

same name siblings is repository specific behavior. cmis does not define uniqueness or how to handle non-unique scenarios.

Description

« Hide

reported in various discussions during the PlugFest in Basel, my interpretation may be off.

It would be great to have at least a "get folder by path" that allows to reflect the
hierarchy that we expose through the parent child relationships of folders.

Generally there are a lot of usecases (exposure to filesystem like trees, relative links from document to documents) that would
benefit from a path. This does not stand in contrast with having multiple paths to the same document or folder.
Is anyone opposed to introducing paths into CMIS?

All

Comments

Change History

Sort Order:

[ Permalink | « Hide ]

Jens Hübel added a comment - 06/May/09 03:45 AM

just to make it a bit more complete some problem areas having been discussed around this (please add what is missing):

do we need getFolderByPath() or getObjectByPath()?

Issue: same name siblings, a repository might support more than one item having the same name. In this case it could not implement this function. Should it just throw a specific exception in this case?

do we need a mapping in both directions? In the other direction multi-filing would be an issue (no unique path to an object).

Should path navigation be an optional capability of the repository?

Therefore might be tough to specify. However path navigation is such a common pattern (file system, URL, WebDAV, ..) that we really should think about if this isn't the 80% part and the issues are the 20%...

Use Cases: WebDAV mapping, simple CMIS browser based on URLs

All in all it would be good to get a decision from the TC how to deal with this as this issue arises over and over again.

[ Permalink | « Hide ]

Julian Reschke added a comment - 06/May/09 03:56 AM

Agreed in general.

One comment: the path really should identify a single object. With same name siblings this essentially means that you need to make an index part of the path, just like in JCR.

[ Permalink | « Hide ]

Al Brown added a comment - 04/Jun/09 05:56 PM

see 169; separate folder names with /, represent root folder with '/'. thus '/abc/def/ghi'; abc is the name of the folder under the root folder; def under abc; ghi under def.

[ Permalink | « Hide ]

Alpesh Patel added a comment - 10/Jun/09 04:15 PM

This would require folder titles exclude (or encode) '/' chars, which may not be a problem.

Not sure how this would be mapped to RESTful binding since the folder names might not conform to a URL (e.g., spaces, punctuation). It would probably need to be a query string parameter, e.g., /folders?folderPath=%2Fabc%2Fdef%2Fghi