Insert logical cloud location for all documents automatically

🏷️ General
, , ,
1

I have no support/technical question and have seen the support category. (Be aware that direct support questions will be deleted.)

on

Which general topic do you have

Hi :slight_smile:

I do not know if I post in the right section. In this case could you move it in the fitted section.

We are french and let is train an association under the 1901 law in the aim of reach food autonomy. Our web hosting provider is Framasoft a french popular education association under the 1901 law too which housing a NextCloud technology and we me made the choice to use the Collabora suite for editing our documents.

As far as I am concerned I am a simple volunteer participant in the collective.

We store our documents in a cloud tree, and I asked to myself if it can be possible to auto insert the location in all documents (for example from header or footer) because it will be more comfortable to find it.

I discovered we can insert a file location field (Document > File name > Path/File name) but when I did it I stared it is the temporarily real system location like /tmp/user/docs/<alphanum_string>/260114.odtwhich is usefulness for users and do not indicates the document is inODJ & CR / COORDO / CR / 260114.odt` cloud tree.

I dug further and it will seem the WOPI protocol which can make communication between NextCloud and Collabora does not expose the logical folder tree.

Have I understood correctly ?

I suppose it is possible to modify this behavior in order to add a new custom field, modify the default template, or run a macro that performs the same operation.

I imagine it is possible, but for this moment I do not administrate nor the NextCloud configuration, nor the Collabora configuration. What I wish is to have the simplest way to indicate how to achieve this to our tool administrator or assist her/him.

Is it easily possible for now in our scope ?

Here is our NextCloud/Collabora version information :

COOLWSD version: 25.04.7.3(git hash: a0576a3364)
LOKit version: Collabora Office 25.04.7.3(git hash: 4ad7ba3245)
Served by: unknown
Server ID: d4e2c7a1
WOPI host: nextcloud 31.0.9.1 - richdocuments 8.7.5

Thank you in advance for the time you will spend to help us.

With adelphity :slight_smile:

lnj

2

Hello @lenainjaune,

welcome to the Nextcloud community! :handshake:

Good point I’m really wondering nobody asked before. I think it’s better to ask such specific question in Collabora forum.

3

Hi and thank you for the time you spend to us :wink:

In fact I posted on the Collabora forum and they say that the problem would be mainly related to the WOPI protocol which will not expose the logical cloud path. For what I understood this protocol would permit NextCloud to communicate with Collabora and own to Microsoft and thus would not be an Open Source project.

I asked to myself if in our scope we can modify what is exposed by this protocol.

Here is the thread : Insert cloud location for all documents automatically - #5 by darshan - User Support - Collabora Online

1 Like
4

I do not understand why my thread was marked as resolved as I do not found a way to achieve this.

I just said that I previously post on Collabora forum but there they said for now LibreOffice does not receive exposed cloud logical path as the WOPI protocol does not expose them.

Then I imagined to discuss this functionality with the NextCloud staff’s project.

I have some development knowledge and an understanding of systems and networks. I know that a web server defines logical paths, so I assume that the WOPI protocol could simply needs to transport them to expose them and LibreOffice could thus retrieve them.

Am I wrong ?

5

Feel free to unset the solution mark if you like.. There are many reasons why I resolved your thread. Mostly because you open a topic on collabora forum where it is placed much better and on the other side there will be no good outcome in this forum (and the question is also not in scope of the forum) because not many Nextcloud Devs attend here and the best way to “discuss” with them is Github (which is mostly unsatisfying as well).

1 Like
6

OK this seems to be the end of my weak hope :grinning_face: …

Resolved as I can not go further.

Thank you for your help :+1:

See you soon :grinning_face: