Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Introduction

XTM Cloud offers a quite enhanced feature which allows for keeping track of almost all changes performed within the framework of a single project in XTM Cloud. It enables you to check, among others, such things as:

  • Names of the constituent files, users,

  • Target languages,

  • Specific actions performed,

  • Objects of the actions performed.

The feature in question is called Project history and is manifested in the form of an XLSX file. It can be generated and downloaded by Project Managers, directly from the project’s context menu, from XTM Cloud [Projects → Project list → Simple search → (click on three dots next to a relevant XTM project) → Download → Project history].

2024-10-15 15_33_21-Window.png

What does the Project history report contain?

The Project history report consists of a few columns. Each one provides a row with a different significant piece of the overall information which gets formed by putting together all the pieces in a single row.

The following table describes each column in detail.

COLUMN

DESCRIPTION

Date [TIME_ZONE]

This column displays actual date of a particular event. The date is presented in the format which has been selected for a particular user who downloads the file, in the XTM instance, in Configuration → User details → General info → Date format.

The time zone which appears to the right of the date is presented in the format that has been selected for a particular user who downloads the file, in the XTM instance, in Configuration → User details → General info → Time zone.

User ID

This column displays ID of the user who triggered a particular event. The ID is taken from the user information, in Users → User list → (find a relevant user) → tooltip → ID.

User name

This column displays username of a user who triggered a particular event [Users User list → (select a user) → General → General infoUsername].

LSP ID

This column displays ID of the LSP who triggered a particular event, if this was the LSP indeed [Users → LSPs → LSPs → (find a relevant LSP) → tooltip → LSP ID].

LSP name

This column displays company name of the LSP who triggered a particular event, if this was the LSP indeed [Users → LSPs → LSPs → (select a relevant LSP) → General → Company name].

Job ID

This column displays ID of an XTM job within the framework of which a particular event occurred. The ID is taken from the related XTM project in the XTM Cloud UI [Project Editor → Workflow → (click on the context menu of a relevant XTM job) → Additional job details → Job ID].

Project ID

This column displays ID of an XTM project, within the framework of which a particular event occurred. The ID of the XTM project can be found in a couple of places in XTM Cloud. The value in the column is identical across all the rows in the entire file.

For more information, read the following article: How to find a project ID.

Project name

This column displays name of the XTM project, within the framework of which a particular event occurred. The ID of the XTM project can be found in a couple of places in XTM Cloud. The value in the column is identical across all the rows in the entire file.

For more information, read the following article: How to find basic contact details (URL, company name, project name).

Target language

This column displays project’s target language within the framework of which a particular event occurred.

Pay attention to a relevant target language if the project in question contains more than one target language (Project Editor → Workflow → Target language).

File name

This column displays name of the source file within the framework of which a particular event occurred. Source files' names can be found in Project Editor → Workflow.

Action name

This column might be the most important one in the entire report since it displays information about a type of specific action that took place within the framework of a particular XTM project.

See project-related actions registered in the report below:

  • Project created → Project creation.

  • Completed analysis of the project → Project analysis completion and each subsequent project reanalysis.

  • File added → Adding a source file to the project.

  • Workflow assigned - PM (it was performed by a Project Manager) → Assigning linguists to at least one workflow step and saving the changes.

  • Workflow started - PM → Clicking the Start button.

  • XTM Workbench opened (PM or Linguist) → Entering the editor by either a Project Manager or a Linguist.

  • Workflow active steps changed (PM or Linguist) → Transition between workflow steps triggered either by either a Project Manager or a Linguist.

  • File generated → Generating a project-specific file: it can be Target, XLIFF for offline translation, etc.

  • File uploaded (PM or Linguist) → Uploading a project-specific file back to the said project: it can be Target, XLIFF for offline translation, etc.

  • Workflow changed in a popup window → Change of the workflow definition for a particular XTM job, performed in the Workflow editor.

  • Moved forward to step → Transition of the workflow to the next step performed by a Project Manager directly in the Workflow section, and not by finishing tasks in XTM Workbench.

  • Task finished (PM or Linguist)→ Finishing a task in XTM Workbench by either a Project Manager or Linguist.

  • Workflow finished (PM or Linguist)→ Closing a particular workflow by either a Project Manager or a Linguist, by finishing the very last step in this workflow.

  • Project archived → Archiving a project in the XTM Cloud UI.

  • Project activated → Activating a project in the XTM Cloud UI.

  • Project saved as template → Creating a new XTM project template by clicking the Save as template button in the Workflow section.

  • GENERATE_TERM_EXTRACTION → Extracting terminology from the project. For more information, read the following articles:

  • TM Approved → Approving TM for the project from the project’s context menu in the XTM Cloud UI (Actions → Approve TM for this project).

  • Project TM approved → Project TM approval process completion.

  • Project leveraged and ICE segments accepted → Accepting Leveraged and ICE segments for the project from the project’s context menu in the XTM Cloud UI (Actions → Accept Leveraged & ICE segments).

  • Project history downloaded → Downloading the Project history report.

Additional information

This is probably the second most important column in the report since it mostly displays more detailed information about the action described in the corresponding row in the Action name column.

For some actions triggering a specific change, the column indicates the object of the change, whereas the for other actions the column provides more details. Some actions are not accompanied by any additional information

See examples below:

  • Project created: Customer: TestCustomer, due date: 15-10-2024 10:00.

  • Completed analysis of the project: Customer: TestCustomer.

  • File added: Added to a project.

  • Workflow assigned - PM:

    • Correct 1: Segments 1-13: Linguist2 Linguist2 (Linguist2)

    • Translate 1: Segments 1-13: Linguist Linguist (Linguist).

  • Workflow started - PM: –

  • XTM Workbench opened: Translate 1 step, segments: 1 - 35, 36 - 71, Edit mode, Hello.

  • Workflow active steps changed: Was: Translate 1, now: Translate 1, Correct 1.

  • File generated: Target.

  • File uploaded: XLIFF: The meaning of a word is in its use in a language - source.docx.xlf.

  • Workflow changed in a popup window: Was: [Translate 1, CAT Tool Step, No approving TM, No due date] -> [Correct 1, CAT Tool Step, Approving TM, 15-10-2024 10:00], now: [Translate 1, CAT Tool Step, No approving TM, No due date] -> [Correct 1, CAT Tool Step, Approving TM, 15-10-2024 10:00] # [Review 1, CAT Tool Step, No approving TM, No due date].

  • Moved forward to step: Translate 1 to Correct 1.

  • Task finished: Segments: 1 - 13, review1 1, due date: 30-10-2024 11:00.

  • Workflow finished: –

  • Project archived: –

  • Project activated: –

  • Project saved as template: Name: Exemplary template, type: Customer specific, description: Description.

  • GENERATE_TERM_EXTRACTION: –

  • TM Approved: –

  • Project TM approved: –

  • Project leveraged and ICE segments accepted: –

  • Project history downloaded: –

IMPORTANT!

Keep in mind that actions performed via API were not included in the table above. Not all API actions are registered in the Project history report.


Project history vs file history

  • No labels