Workflow
Learn what are projects and document and how they flows into TextMaster architecture.
Last updated
Learn what are projects and document and how they flows into TextMaster architecture.
Last updated
A project is the base of the process. It is the main element determining the general and common characteristic to all the types of projects:
Translation
Copywriting
Proofreading
A project holds metadata such as language pairs, category, general briefing, author assignment methods, templates, options, etc. It's a placeholder made of one or multiple documents.
Projects follow a logic succession of statuses. The accessible steps are represented in the diagram. The definition of each status is given in the table. Some transitions are triggered by the client, other result from document status, you'll find more details about "how" a project got into this state in the table below.
Status | How | Definition |
---|---|---|
| Initial status. | Project is not accessible to authors, the client can edit the project and add or remove documents from it. |
| The client launched or resumed after being paused the project. | Project is available to be claimed by authors, the client can't edit the project anymore. |
| Depends on document(s) status(es). | All project's documents were submitted and are in internal quality control or |
| Depends on document(s) status(es). | All project's documents are |
| The client paused the project. | Project is not accessible to authors. Only documents already claimed remain accessible. |
| The client canceled the project. | Project is not accessible to authors. Only documents already claimed remain accessible. Client is refunded for un-claimed documents. |
A document is the element corresponding to the expected content to be worked on. It's attached to a project and its characteristics are specific. If many documents may share the same characteristics within the same project, they may also all be different.
Documents follow a logic succession of statuses. The accessible steps are represented in the diagram. The definition of each status is given in the table. Some transitions are triggered by the client or the author, you'll find more details about "how" a document got into this state in the table below.
Status | How | Definition |
---|---|---|
| Initial status. | Document is not accessible to authors and the client can edit the document. |
| After the project has been launched or resumed after being paused by the client. | Document can be claimed by authors. The client can't edit the document anymore. |
| The author has claimed the document. | An author has claimed the document and is working on it. |
| The author has submitted the document's work and document has successfully passed through the quality controls (if required). | Document is now under the review of the client. |
| The client has completed the document which terminates the workflow. | Document is now completed and the author has been paid for the work done. |
| The author asked a question, the client requested a revision or automated quality control checks failed. | Document's work has been started but is not completed yet. |
| The client paused the document. | Document is not accessible to authors. |
| The client canceled the document. | Document is not accessible to authors and the client is refunded. |
| The author has submitted the document's work. | This step is specific to copywriting activity. Plagiarism detection analysis is being run on the document. |
| The author has submitted the document's work. | This step is specific to copywriting activity. We are counting words written and running a few quality checks. |
| Depends on the project status. | Quality control checks are being run on the document. |