What is the best way to work with a package received by the client when we have different steps and different participants to the project?

Hi everyone,

One of our client changed his method and now sends us packages. Since we work with various participants, we are not sure how we can work to be as efficient as possible. I am not used to working with packages.

When we receive the project (WorldServer Project with only file-based TMs), we want to be able to add our own TM and then send the file to our translator. When the translator is done, we have to send the file to the reviser and then when the reviser is done, we need to do a quality check internally. For our client's delivery, we need to deliver a Return package.

We are several project managers and we should be able to open the files on any computers internally (and not only on the computer that first opened the project).

We are used to work with file and thus to extract the file from the Packages we receive and to deliver only the sdlxliff file but now that we have to deliver return packages, everything changes.

Do you have any ideas on how to proceed (in the most efficient way) ?

Thank you very much,

Marine

Parents
  • Hi,

    A couple of other alternatives, but it all depends on your setup of course.

    GroupShare:
    Might be an option if you are sharing projects on a regular basis and your company is of a certain size, so that it's worth the investment.

    Poor man's GroupShare:
    1. Pull out the SDLXLIFF's from the client's package. (Tip: Associate the SDLPPX and SDLRPX file extensions with your ZIP application, that way you can just double click packages and they will open in the ZIP application instead of Studio.)
    2. Create a master project on the file server. This could be the package project, but since you would have to go through all settings in it, it is probably easier to create your own project. The master project will only be used for delivery, not working. Keep your TM's on the file server.
    3. Everyone involved in the project either copies the master project from the file server to their C:\, or creates their own project on C:\ with the same files as the master project (use the target files of the package as your source files). Then share the only SDLXLIFF's on the file server as necessary. Anyone who needs the translated/reviewed/checked version of a certain file picks it up from the file server.
    - This way there will be no clashes between people writing to the same SDLPROJ file. But it also demands some communication among you about who does what and when.

    In my opinion packages are nice and handy to send out, but they are not as fun to receive (neither SDLPPX nor SDLRPX), since you have no control of what they contain or how they behave.

    Daniel Fransson | SDL Sweden

Reply
  • Hi,

    A couple of other alternatives, but it all depends on your setup of course.

    GroupShare:
    Might be an option if you are sharing projects on a regular basis and your company is of a certain size, so that it's worth the investment.

    Poor man's GroupShare:
    1. Pull out the SDLXLIFF's from the client's package. (Tip: Associate the SDLPPX and SDLRPX file extensions with your ZIP application, that way you can just double click packages and they will open in the ZIP application instead of Studio.)
    2. Create a master project on the file server. This could be the package project, but since you would have to go through all settings in it, it is probably easier to create your own project. The master project will only be used for delivery, not working. Keep your TM's on the file server.
    3. Everyone involved in the project either copies the master project from the file server to their C:\, or creates their own project on C:\ with the same files as the master project (use the target files of the package as your source files). Then share the only SDLXLIFF's on the file server as necessary. Anyone who needs the translated/reviewed/checked version of a certain file picks it up from the file server.
    - This way there will be no clashes between people writing to the same SDLPROJ file. But it also demands some communication among you about who does what and when.

    In my opinion packages are nice and handy to send out, but they are not as fun to receive (neither SDLPPX nor SDLRPX), since you have no control of what they contain or how they behave.

    Daniel Fransson | SDL Sweden

Children
No Data