Accepted, Not Yet Planned

This is a nice idea but is currently not planned. We're looking for additional comments and feedback on the use case here.

  • Do users want such potential statuses to be exactly like the Publishing Queue (a few statuses)?
  • Or is the idea to have the ability to prioritize the entire list by jobs?
  • And is this just on retrieval?

Translation Manager's job is to move jobs back and forth between systems. Unless you're dealing with large amounts of translation that even machine translation takes time on, it's not enough to prioritize work from a system perspective. The work would need to be prioritized in the translation management system, down to letting translators know what to work on first.

Allow Users to set a retrieval 'priority' on a Translation Job.

Among Job A, Job B and Job C, I want Job B to be picked up by the Translation Manager service first for e.g: my "Flash Sale", however Translation Manager does not have the possibility to prioritize the retrieval phase.

Paul Brou
Parents

  • gave me some insightful advice on the parallels between publishing and translation (both being queues of submitted work). Users would expect the same features in TM jobs as the publishing queue and vice versa (as seen in a few ideas for TM jobs on SDL Web Ideas).

    I'm not sure what we'll pick up yet, but let me leave this open to let others add feedback. Maybe we could collaborate on some type of comparison matrix to see how they really line up...

Comment

  • gave me some insightful advice on the parallels between publishing and translation (both being queues of submitted work). Users would expect the same features in TM jobs as the publishing queue and vice versa (as seen in a few ideas for TM jobs on SDL Web Ideas).

    I'm not sure what we'll pick up yet, but let me leave this open to let others add feedback. Maybe we could collaborate on some type of comparison matrix to see how they really line up...

Children
No Data