Possible to create read-only TMs?

Is it possible to create read-only translation memories, i.e. TMs that can not be overwritten?
I'm aware that one could instead just uncheck the "update" option for a TM in settings, and that would have the same effect, but that is not what I am looking for.

Parents
  • Hello ,

    As you haven't explained exactly what it is you are looking to achieve (and you simply don't want to 'not update) maybe you wish to share TM's that should be read only perhaps and not write/copy

    You can set the TM access as you wish

    Trados Studio Translation Memory Settings window showing access rights options including Administrator, Maintenance, ReadWrite, and Read-only with a field for Administrator password.

    There are four levels of access

    1. Administrator: Can perform any TM-related operation, i.e. read/write, change settings, import/export.
    2. Maintenance: Can perform operations such as global find/replace in a TM (but no change of TM settings and no import/export).
    3. Read/Write: This access level is typically used by translators, who need to be able to add/change TUs and search the TM.
    4. Read-only: Guest access that allows users to perform TM look-ups.

    Then once the TM is added to the project- this needs the correct password

    Translation Memory Password prompt in Trados Studio with dropdown menu for Minimum access mode options: Guest, Translator, Maintenance, and Administrator, and a field for an optional password.

    Is this what you are looking for?

    Oana Nagy | QA Engineer | RWS Group

    emoji


    Generated Image Alt-Text
    [edited by: Trados AI at 11:55 PM (GMT 0) on 28 Feb 2024]
  • Hi! This is a LONG since due answer.

    What we'd like to achieve is a foolproof way of making sure no one of us accidentally marks the "update" box for one of our background memories. We still want to see matches from that memory on top though, which we can manage by having that as the first memory on the list. However, since we're all humans, we're a bit afraid of the human error and would like to avoid the risk of someone forgetting to untick the "update" box...

    Do I understand correctly, that even if someone is set as "Read/Write" only (ckass 3 above), they could still potentially make this mistake?

Reply
  • Hi! This is a LONG since due answer.

    What we'd like to achieve is a foolproof way of making sure no one of us accidentally marks the "update" box for one of our background memories. We still want to see matches from that memory on top though, which we can manage by having that as the first memory on the list. However, since we're all humans, we're a bit afraid of the human error and would like to avoid the risk of someone forgetting to untick the "update" box...

    Do I understand correctly, that even if someone is set as "Read/Write" only (ckass 3 above), they could still potentially make this mistake?

Children
No Data