• State Suggested Answer
  • Replies 19 replies
  • Answers 4 answers
  • Subscribers 434 subscribers
  • Views 16004 views
  • Users 0 members are here
Options
Related

Is it possible to choose another location of the "Studio 2015" folder than in the "Documents" folder?

Marie Lund

I am about to install Studio 2015, and I am wondering if it is possible to choose another location of the "Studio 2015" folder than in the "Documents" folder?

More specifically, I might want to put it in my Dropbox folder for the purpose of automatic backup. I am also considering putting it on a different drive on my computer in order to be able to access it from outside of Windows (since I run Windows in a VirtualBox environment on a Linux computer).

Can this be done - perhaps during installation and setup? And if so, how?

Can it also be done later on?

Thanks in advance for any help!

Marie
Rate translation
×
Suggest better translation
×
Moderator UI
×
  • Get AI Suggestion
  • 0 in reply to Paul Filkin
    Dear Paul, thanks again. I think I understand your point now.

    It may seem like I have no particularly good reason for wanting to move the Documents folder, but I think I do, and I think this would in fact be the right solution for me. It will mean a little extra work here and now, but later on, this set-up will be very convenient for me.

    My reason for wanting to locate all my projects on a different drive is the fact that I run Studio on a virtual Windows machine inside a Linux machine, and it would be practical to be able to access all files - especially the final target files - without having to start Windows every time. Therefore, I want my project files in a shared folder that I can access both from both "machines". Such a shared folder can be created in Linux and would appear to Windows simply as a new drive. I already have many such shared folders, so the new "drive" would appear as drive M.

    So why do I want to move the entire Documents folder there, then, and not just my projects? You have mentioned the reason yourself: It would allow Studio to do what it wants to do and put everything in the Studio default folder. I would be fiddling as little as possible with the default file and folder structure by simply moving everything in one go.

    The only other change I will probably also make is creating per client sub-folders in the "Project" folder and placing my project folders there:
    M:\Documents\Studio 2015\Projects\Client1\Project1
    M:\Documents\Studio 2015\Projects\Client1\Project2
    M:\Documents\Studio 2015\Projects\Client2\Project1
    etc.

    Does it make sense now?
  • 0 in reply to Jerzy Czopik
    Hi Jerzy,

    I still wouldn't move the documents folder for this, I'd just store the stuff somewhere else. But I can see your point and for you I think managing something like this (moving the location of the Documents folder itself) which is a little like fighting against the flow is less problematic. If you're technical these things are always manageable, but I'd always advise users not to do this unless they are really comfortable with what they're doing and are happy to deal with problems that can occur when windows updates, and programs won't play ball.

    But that's just my opinion :-)

    Cheers

    Paul

    Paul Filkin | RWS

    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul Filkin
    I see your point, Paul. I am planning to stick with Windows 7 as long as it is supported (or as long as my laptop continues to function). So I am not planning to upgrade to Windows 10. Do you think normal updates are likely to cause any problems?

    I guess your answer will be: Probably not, but one never knows.

    So okay, better safe than sorry. So like I just said in my other thread ("Moving existing project files to a different location"), maybe I should just leave the Documents folder where it is and only move my projects.

    Are the files which must remain in the Documents\Studio 2015 folder important in the sense that I should back them up regularly, or can I just back up my TMs and projects and forget about the files in the Documents\Studio 2015 folder?
  • 0 in reply to Marie Lund

    Hi Marie,

    Unknown said:
    Do you think normal updates are likely to cause any problems?

    You might never have any problems so I can't really say... but I'd just avoid it because too many applications use this stuff by default and Windows almost forces that policy as much as it can.

    Unknown said:
    Are the files which must remain in the Documents\Studio 2015 folder important in the sense that I should back them up regularly, or can I just back up my TMs and projects and forget about the files in the Documents\Studio 2015 folder?

    I think it's your resources and working files that are the most important.  So I'd back up the projects, the TMs the Termbases, the AutoSuggest Dictionaries... basically anything that I had to spend time creating.  The rest you can easily put back as they are just metadata telling Studio where to find them.  If I had hundreds of open projects because I worked as a Project Manager for a large LSP for example then I might consider trying to do something with the projects.xml, but otherwise I'd just reopen the projects I wanted if necessary.

    There are also more resources in the user folders that Studio doesn't share very well, such as AutoCorrect lists and also resources your can export import like QA settings.  So getting everything is a real chore and we have tried to get some interest through the AppStore community in extending a tool to help manage all of this.  But sadly it's still languishing as a good idea that never took off :-(

    Would be better if Studio itself just had an archive facility or backup facility that allowed an easy backup and restore of everything!  Interestingly after two months of giving people the opportunity to ask for an idea to be built that they liked this one never came up (other than a couple of people asking for a project archiving tool), so maybe it's not really anything people worry that much about anyway... at least not until they need to move computers!!

    Regards

    Paul

    Paul Filkin | RWS

    Design your own training!
    You've done the courses and still need to go a little further, or still not clear? 
    Tell us what you need in our Community Solutions Hub

  • 0 in reply to Paul Filkin
    Thanks, Paul! I'll just forget about backing up the files in the Documents\Studio 2015 folder, then.
  • 0 in reply to Paul Filkin
    I see how this allows us to locate project files. But there seem to be other things in the (in my case) Studio 2017 folder. There's a projects.xml file in a Projects folder that won't get moved with this approach, I think. How can we move it all - that, and the Projects Templates folder (+ its contents), plus the Upgrade Translation Memories folder (+ its contents), plus (what I have, anyway) Plugin.Bookmark.xml and Plugin.Symbols.xml?
  • 0 in reply to John Narins
    Just found this old nugget and because I'm stumbling over this stupid problem every time I (re-)install Studio it's now added here for me to find:

    The location of the projects.xml file is NOT hard coded (phew!) but stored in file

    %appdata%\SDL\ProjectApi\XX.0.0.0\Sdl.ProjectApi.xml

    (obviously replace XX in the above path with the appropriate number of your version: 12 for 2015, 14 for 2017, 15 for 2019 ...
  • 0 in reply to Angela Sigee
    Yup, I'm using this file to manipulate the projects list location since Trados 2007 ;-)
  • 0 in reply to Angela Sigee

    Thanks! 

    Mine is now here: C:\Users\[username]\AppData\Roaming\SDL\SDL Trados Studio\Studio16\Sdl.ProjectApi.xml