[EXCONTRANS-377] Tasks per language * per workspace for batches with multiple resource nodes Created: 07/Jun/22 Updated: 04/Oct/22 Resolved: 04/Oct/22 |
|
| Status: | Closed |
| Project: | Content Translation Extended (CTX) |
| Component/s: | Core |
| Affects Version/s: | 3.4.5 |
| Fix Version/s: | 3.4.6 |
| Type: | Improvement | Priority: | Medium |
| Reporter: | Florian Kugler | Assignee: | Teresa Miyar |
| Resolution: | Workaround exists | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
Current: When creating translationBatches with many resource nodes (mgnl:translationResource) from different workspaces and multiple target languages the module currently creates a task for each resource node per language. While Steps to reproduce:
Having a batch with N different resource nodes and 5 target languages we still get N x 5 tasks. Expected result:
|
| Comments |
| Comment by Riste Drangovski [ 07/Jun/22 ] |
|
Current logic is that for each resource node in the batch and for each target language we create a new submission item. As a workaround (based on the scenario/steps to reproduce the issue): |
| Comment by Florian Kugler [ 08/Jun/22 ] |
|
Hi Riste, thanks for the update! Best regards, |
| Comment by Riste Drangovski [ 08/Jun/22 ] |
|
Hi Florian, Because this involves a lot of effort on our side (it's not a small change) and I don't see this as bug (it's how it is by design), we need to discuss this internally. I guess, me or Teresa will give you update (in the next couple of days), if this is something that we are going to work on or leave it as it is. Regards,
|
| Comment by Florian Kugler [ 08/Jun/22 ] |
|
Hi Riste, thank you for the info, I will wait for your decision then Best regards, |
| Comment by Teresa Miyar [ 10/Jun/22 ] |
|
Hi Florian, We have investigated your request. In Magnolia, we work with hierarchical data. This means that whenever you would export anything from anywhere (be it a workspace, directly from the content app, etc.), it will need a hierarchy to be able to create a document (YAML or XML) out of it. Regards, Teresa. |
| Comment by Florian Kugler [ 07/Jul/22 ] |
|
Hi Teresa, thank you for your detailed answer! We will think of developing a custom implementation with those specific needs on our side then, since the workaround provided does not work in our project setup. Thanks for investigating! Regards, |