ECA Content: Create translation of an existing entity

Created on 24 July 2023, over 1 year ago
Updated 12 June 2024, 6 months ago

Problem/Motivation

I am trying to build another beautiful ECA model that will automatically translate entities using AI via Augmentor or Prompt AI.
When an entity is created, however, its translations are not. I was looking for an action such as "create new translation" or "add translation" in ECA to be able to do this automatically, but I can't seem to find any way of doing this.

Maybe I'm lacking in understanding of D10's translation system, and I'm approaching it the wrong way. Or is this currently not possible with ECA?

Thanks in advance for any guidance on this :)

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Feature request
Status

Active

Version

2.1

Component

Code

Created by

🇹🇭Thailand AlfTheCat

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @AlfTheCat
  • 🇩🇪Germany jurgenhaas Gottmadingen

    Nice use case, and interesting question. I don't know the answer from the top of my head, but will do some research and let you know. If it's bot yet possible, I'm sure we will build a new action to make it work.

  • 🇹🇭Thailand AlfTheCat

    Awesome! Thank you!

  • Assigned to jurgenhaas
  • 🇩🇪Germany jurgenhaas Gottmadingen
  • Issue was unassigned.
  • 🇩🇪Germany jurgenhaas Gottmadingen

    I've looked into this, and it appears, that ECA can't create a translation for an existing entity yet. The Entity: create new action creates a new entity, not a translation of an existing entity. The Entity: load action loads an existing translation of an entity, but doesn't create a new one.

    Several choices to be decided:

    • Should that be a new action plugin or could this be added to the Entity: load action to create a translation if it doesn't yet exist?
    • If it's going to be a new action, should that be part of eca_content or eca_language?

    My preference is to create a new action in eca_content.

    Thoughts?

  • 🇹🇭Thailand AlfTheCat

    I think it should indeed be a new action as part of eca_content. Entity load would be confusing for some users, for it may not be obvious that a translation can be created by loading a non-existent one. I think it fits in the eca_content part because it is a content operation and not yet a specific language operation until the translation for a language is created.

  • 🇳🇱Netherlands rapidr0ll Amsterdam

    +1 Having this feature would be great

  • 🇩🇪Germany jurgenhaas Gottmadingen
Production build 0.71.5 2024