Aug 28, 2019

The challenge of light resource updates with many projects in memoQ

"Templates" take two forms in memoQ: the configuration option for equipping new projects with relevant resources in an automated way to save time and avoid forgetting important references or other information, which was introduced several years ago, and the older sort of "template" - a configured, existing project for a particular client or subject area - where new documents are simply added and old ones archived or deleted as time goes by. I use both approaches and still tend to rely more on the latter practice, as many do.

One colleague who is a frequent source of inspiration for new workflow approaches often mentions that her projects and support resources number in the hundreds, so many ideas I have for managing my own more limited set these days are not practical for her work. But recently someone mentioned casually that it was going to be difficult to update segmentation rules in the 1500 or so projects that her team maintains to support in-house translation needs in their firm. Oh, my God. Yes, that would take some time following the usual approach of going to Project home > Settings and selecting a new resource in even 10% of that number of projects.

There is a better way. In fact, this way will work with the desktop editions typically used by individuals as well as with memoQ server installations of any size, and a "mass update" of project light resources can be performed in very little time - less than it usually takes me to finish a cup of coffee in the morning. My recent article on memoQ light resource defaults and how to change them essentially points the way, but more details, now tested with a memoQ server as well, are given here.

Light resources in a desktop edition are typically stored in the paths
C:\ProgramData\MemoQ\Resources\Defaults for default resources and
C:\ProgramData\MemoQ\Resources\Local for customized (user-created) resources, unless that path was changed (as many do if they deal with a lot of files with long names and need to shorten paths to avoid errors when the file and path names together approach the 256 character limit imposed by Microsoft Windows).

Server installations follow more or less the same logic:
C:\ProgramData\MemoQ Server\Resources\Defaults for default resources and
C:\ProgramData\MemoQ Server\Resources\Local for custom ones, unless changed as noted above.

Note that the ProgramData folder is a hidden folder by default in Windows, so you may need to change your folder settings to view it.

Light resources stored in both the Defaults and custom (Local) folders are saved without the MemoQResource header one sees in an exported light resource file. Compare the following two screenshots of the same resource in the external editing and maintenance file (with XML comments to help me keep track of what things mean) and the stored file after importing it into memoQ:

My master resource file for German segmentation, maintained with comments in Notepad++
Imported custom resource file for German segmentation. All comments are stripped by memoQ.

So, what should you do if you have 200 projects for your personal work with a memoQ desktop edition or 1500 projects on your memoQ server, and you have a new segmentation rules file, for example, which you want to apply to all of your projects? Simply
  1. Copy all the text beginning with the XML declaration

    all the way down to the end of the file.
  2. Find the default or local resource to update in the paths described above (or in your own custom path) and open the file in a text editor.
  3. Select all the text in the installed resource file, and paste the text of the new resource over it, replacing the content completely.
  4. Save and close the file.
The changes to your default or custom resource will be active immediately. No need to restart memoQ or close and re-open any projects.

In my case, with the German segmentation file given as an example, I would paste that new content into the resource files for generic German (ger), as well as German from Germany (ger-DE), Austria (ger-AT) and Switzerland (ger-CH). No need to mess with the awful integrated resource editors in memoQ, because I keep a master resource file with explanatory comments to help me maintain it better outside of memoQ, and the segmentation I want will be the same for all language variants.

This method does nothing to disturb the content of existing projects nor does it affect their stability in any way. This should work with any memoQ light resources. Thus, for example, an IT department could plan bulk updates even of local resources like keyboard shortcut or web search settings given the necessary access to user drives on a network.

The approach that many follow of deleting old resources and importing new ones with the same names won't work; this can play Hell with project settings, because memoQ notices that a resource used in projects has been removed, and it does not replace the old assignment with a new one, even if that new one has the same name. I played that game with many variations to see if I could trick memoQ into substituting the same-named resource in my project and had no success at all. Don't go there. Use the process I described above.

1 comment:

  1. Hi Kevin, that's very apt!, Well expressed! Thanks for post.


Notice to spammers: your locations are being traced and fed to the recreational target list for my new line of chemical weapon drones :-)