We have run into multiple difficulties with GroupShare (on-premise), with spats of difficulties occurring on and off since we first installed the software, and we are balking at changing over to GroupShare Cloud. Before we initially upgraded to GroupShare, I was struggling with the file-based memories and termbases, because we had multiple teams going at the same time that needed access to the same memory, but we couldn't share it successfully with the files.

Now I'm back in the same place, and I'm wondering if anyone else has additional ideas. We tried storing the file-based on a network drive (not allowed), Dropbox (but that kept overwriting the previous memory instead of adding to it), and then just assigning one team to each client and having the jobs wait in a queue (which then meant jobs were taking too long to deliver). In this industry, it seems if it rains, it pours, and when it's dry, it's the Sahara, so it's hard to gauge if the expense of the service and corresponding support will be worth it.

We also had the different teams emailing each other as they added terms to the termbase, but that became awkward and the terms weren't always consistent in the actual Studio file.

As far as I can tell, there is no sustainable method to handle multiple projects (with multiple teams) and one file-based memory/termbase combo. Does anyone else have any ideas?

Thank you,

Joanna