Projects stage 2: project TMs and glossaries

[ArchiDevil]

Stage 2: it is possible to set up project TMs and Glossaries for the project. It is possible to upload new files in projects only. TMs and Glossaries are used in every file in the project.

Backend requirements:

• Project-Level Translation Memory (TM) Association
  The system must allow users to link one or more Translation Memories to a project, with each TM supporting a read mode (for lookup) or write mode (for storing new translations). Users should be able to add, remove, and update TMs associated with a project.

• Project-Level Glossary Association
  The system must allow users to link one or more Glossaries to a project. Users should be able to add and remove Glossaries associated with a project.

• File Upload to Projects
  The system must allow users to upload files directly to a project, automatically associating the file with that project. New files should be uploaded to projects rather than as standalone documents.

• Automatic Resource Inheritance
  When a file is created within a project, it must automatically inherit all TMs and Glossaries associated with that project. The system should automatically apply these resources during document processing.

• TM and Glossary Search in Project Files
  When searching for TM matches or glossary terms for a document, the system must search across all project-level TMs and Glossaries and aggregate the results.

• Automatic TM Updates (Write Mode)
  If a project has a TM configured in "write" mode, new translations created or approved in any project file should be automatically added to that TM.

• Project Resource Visibility
  Users must be able to view all TMs and Glossaries associated with a project, including details such as name, record count, and mode (for TMs).

• API Endpoints for Project Resources
  The system must provide endpoints to add, remove, and retrieve TMs and Glossaries for a project, as well as upload files to a specific project.

Frontend requirements:

• Project-Level TM and Glossary Configuration
  Users must be able to assign specific Translation Memories and Glossaries to projects directly, establishing these as default resources for all documents within that project. This configuration should be accessible through a project settings interface that allows users to select which TMs and Glossaries apply to the entire project.

• Project Selection During File Upload
  When uploading new files, users must select a target project from a list of available projects. The upload interface should clearly display project options and prevent file uploads without a project selection, ensuring all documents are properly organized within projects from the moment they are created.

• Project Settings Management Interface
  A dedicated settings interface for projects must provide users with the ability to view, add, remove, and modify the TMs and Glossaries associated with a project. This interface should be easily accessible from the project list or project detail view and provide clear visual feedback about which resources are currently configured.

• Project-Level TM Write Mode Configuration
  Projects should support configuration of which Translation Memory serves as the write target for all documents within the project. This allows users to designate a specific TM where translations from all project documents are automatically stored, maintaining a centralized translation memory for the entire project.

• Display Project Resources on Documents
  When viewing document settings, users should see which TMs and Glossaries are currently associated with the document. This provides visibility into the resources being used for translation assistance without requiring users to understand the underlying inheritance mechanism.