(Internal) Associate translations with domain objects

Registered by Morten Olav Hansen on 2016-04-15

Currently all translations live in the translation table, while this has been working OK for us, it's time to refactor this.

The biggest issue we are struggling with, is translation for deeply expanded fields, i.e.:
/api/dataSets/ID?id,displayName,dataElements[id,displayName]

In this case, only the data set displayName would be correctly translated, as it's too expensive to deeply recursive these objects to do translation.

We need a solution here where the translation follows the actual object (similar to attribute, or user group accesses)

Yes; this means adding one extra table to each metadata type (which is far from ideal), but currently this is the approach we are considering.

Blueprint information

Status:
Complete
Approver:
Lars Helge Ă˜verland
Priority:
Medium
Drafter:
Morten Olav Hansen
Direction:
Approved
Assignee:
Morten Olav Hansen
Definition:
Approved
Series goal:
Accepted for trunk
Implementation:
Implemented
Milestone target:
milestone icon 2.24
Started by
Morten Olav Hansen on 2016-05-18
Completed by
Morten Olav Hansen on 2016-05-19

Related branches

Sprints

Whiteboard

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.