Need ability in Passolo Collaboration Edition for ftp bundle for same language and same project to be synchronized by 3 separate users: Collaboration user, translation user, and translation validator user.  Currently using Passolo Collaboration Edition 2016.

Workflow:

Collaboration Edition user sends out bundles for 2 different purposes:

1.  Bundles sent to SDL for translation of strings missing translation
2. Bundles sent to translation validators to validate the translations that SDL provides.

 If we use Collaboration ftp functionality to share the bundles, It work fine to use it for just one of the 2 (SDL or Translation validator) listed above users. 

The issue is how do we use ftp for both of those 2 users simultaneously?  Currently, appears to only work if used sequentially.

 What appears to be the only Workflow that will work at this time:

1. Collab user exports bundles via ftp for SDL to translate strings missing translations. 
2. SDL translates strings and using Passolo’s ‘Synchronize Export Bundles’ updates the ftp bundle with new translations
3. Collab user selects Passolo’s ‘Synchronize Export Bundles’ to import the new translations to the main Project and releases the bundle license
4. Collab user then exports bundle via ftp to validator. 
5. Validator uses Passolo’s ‘Synchronize Export Bundles’ to update translations base on GUI validation updates
6. Collab user selects Passolo’s ‘Synchronize Export Bundles’ to import the new translations to the main Project and either releases the bundle license if validator is complete, or does not release licensed bundle if validator is not complete.
7. If new strings need to be sent to SDL for translation, then the licenses will need to be released and validator work will have to stop until new translations received from SDL.

Problem:  This means that a given project for a given language cannot be worked on simultaneously by both SDL doing translations and validator making validation edits.  So this is sequential work and not simultaneous.  With this workflow, the Collaboration Edition does not seem to eliminate the reason we switched from Team Edition to Collaboration Edition.

Improvement Idea:

3 types of users - 

User 1 - Collaboration Edition user creates initial bundle exports, and adds updates to source and target language bundles via synchronization to exported bundles.  These user 1 post-export synchronizations add new source string data that are then downloadable by User 2 to translate new strings, and also downloadable by User 3 to pick up new source strings and comments. 

User 2 - pure translation of missing translations.  User 1 synchronization downloads new/changed source records for translation and only updates the ftp bundle to add translations where a translation is totally missing/empty. 

User 3 - translation validator.  User 2 can update the ftp bundle to overwrite translations or any aspect.  As is the case now, a 'T' Comment does not overwrite a 'C' Comment, they are additive.  After user 2 has synchronized new translations to add to same bundle, user 3 sync picks up the new translations from user 2 to validate. 

With this design, all 3 users can synchronize the same licensed bundle throughout the entire validation process for a given project release, for a given language. 

For risk management:

1. Data loss mitigation from overwriting: Do not allow multiple users to synchronize at the same time.  The first user to start synchronization has control of synchronization.  Any other user trying to synchronize at same time will receive a user message stating another user is in the process of synchronization.  Please wait to synchronize later.

2. When license is released on a bundle, all users received e-mail notification that the license has been released so that they know not to try an synchronize.  This should not happen because there is assumed communication between the 3 users when it is time to release the license.  Or maybe from opposite direction, maybe there is a message from user 2 and user 3 back to Collab user 1 when they are finished from their side (user 2- translation, user 3- validation).