path of renamed workspace or section

When one creates a section of workspace the breadcrumb trail, the URL and the path in the REST API to this entity are all consistent with each other. Next we rename the workspace or section. As a result the new name will be used in the breadcrumb trail, however the old name remains in the URL and also this name needs to be used in the REST API. This is a bit troublesome as the titles of renamed items reflect the new name. So this leads to the conclusion that what is on view for the user is potentially different to what is on offer for the programmer. It would be nice for instance to go up a level in the structure through a pathID instead of a fictional breadcrumb pat, but that seems impossible as no such property exists?

What would be the best way to tackle this?

I tried to do this by querying: SELECT * FROM Document WHERE ecm:uuid='some id'. where the ID is the ID of the required section. But this fails. The same is true when I query for Section instead of Document.

1 votes

0 answers

1139 views

ANSWER

"When one creates a section of workspace the breadcrumb trail, the URL and the path in the REST API to this entity are all consistent with each other"

not necessarily : the name of the document may not be the title if the latter is too long or if there is already a document with that name.

05/30/2016

I am facing same issue. path in nuxeo response is not getting reflected after renaming a folder
10/20/2016