4. How to prevent your instance from growing over the limit?
Consider adding these size-reducing measures above to your workflows.
Archive completed projects
Set up a schedule for archiving projects and downloading them from the server. There could be different strategies: Archiving could be done together with wrap-up, or you can archive wrapped-up projects which haven’t been touched for two weeks, etc.
You can remove archive files from the server using manual archiving. Archive files created with the auto-archive feature are not downloadable.
Schedule automated file exports carefully and add the step of downloading exported files and reports to your project management routine.
Don’t translate non-translatable segments
Spending a little time for file preparation pays back. memoQ recognizes segments that contain only numbers (and “translates” those according to the rules of the target language), tags, or items covered by auto-translation rules. Use the Populate numbers-only segments command to populate and lock such segments. This saves translation efforts and prevents storing such items in your TMs.
Schedule resource maintenance tasks
Running QA checks, clearing duplicates and unused old items from TMs and TBs pays back not only by reducing storage size, but also by allowing faster lookups that provide more consistent and up-to-date results.
Use project templates
Project templates help in selecting the right TMs and other resources for your projects and prevent starting new TMs accidentally. To get rid of unneeded working TMs, add an automated action to your templates to delete the working TM at project wrap-up.
Track LiveDocs usage
Abandoned corpora can take up a lot of space. Consider deleting or removing corpora created for one specific project (e.g., for aligning legacy files or distributing references) at project wrap-up.
If you have questions about the topic or need help with your current setup, contact us.
Please sign in to leave a comment.