Creating a project based on a project template Vs. based on a previous project...does one work better than the other?

Dear Studio 2017 experts,

I have always wondered whether creating a project based on template is better than based on a previous project, or vice versa.  I am working on a big project for which I break into smaller projects for easier tracking.  For these smaller ones, I use the same TMs and termbases.  I chose the project template approach, but wonder about how the other option would work.

Can someone shed some lights on these two approaches?

Any information would be great!

Thank you.

Chunyi

Parents
  • Both approaches give the same result, except that in a template you can refine certain details, such as update values for the fields in a TM. Using an existing project simply applies the same values as in that project. If a project is sent to you as an agency package, they may include their TM as a project TM in the package, but you would not want this to be added to another project. You can remove it from the template.

    If you right-click a project in the Projects view, you will find the option 'Create project template' about halfway down the context menu.

    Simon
Reply
  • Both approaches give the same result, except that in a template you can refine certain details, such as update values for the fields in a TM. Using an existing project simply applies the same values as in that project. If a project is sent to you as an agency package, they may include their TM as a project TM in the package, but you would not want this to be added to another project. You can remove it from the template.

    If you right-click a project in the Projects view, you will find the option 'Create project template' about halfway down the context menu.

    Simon
Children