Hi @Tony
My apologies, I read your earlier post too hastily. I didn’t catch the “local folders sync to the same remote location” part 
As I understand it now, your proposed solution would certainly work on the remote user side of our workflow. On the local side, however, we’d still have the same problem of non-adherance to our folder structure. To illustrate, our regular folder structure looks like this:
If a local user needs to access this project’s renders, the user knows to navigate the folder structure by going to the project’s year, project’s quarter, project name, and finally, the folder “renders”. I’m not sure how we’d not bump into an issue of not being able to intuitively find files when we’d be using a separate priority folder.
Oh, also, to clarify, we always keep everything locally synced on our local storage; I just realised that a lot of people use odrive precisely for the selective local syncing - we don’t.
I guess what we could do is to set the priority folders to not sync anything locally, and then actually copy files from our standardized folder hierarchy to the priority folder whenever we need a fast remote sync. That would temporarily create a locally redundant duplicate file, which would be “removed” once syncing is complete, right?
Questions regarding this:
- How does odrive handle the fact that there are duplicate files (one in the correct folder structure, one in the priority location)?
- How does odrive handle the fact that once priority upload is complete, preferrably we’d get rid said priority folder, as it would be locally useless at that point?
Obviously, working with local copies of files still seems kind of a hassle for us. It requires extra manual action and causes unnecessary load on the computer (mainly the HDD) by having to make those redundant copies of files.
Happy holidays!