Add write cmdlets *-IshTranslationJob

[ddemeyer]

TranslationBuilder uses the CMS IshTranslationJob object as leading container to identify which translation stubs need to be created on the CMS side, in which language and which metadata. To then pass control over to TranslationOrganizer who will create the necessary container artifacts in the connected translation management system and pass along the translation stubs with the requested workflow per language.

Goal here is to create a IshTranslationJob that holds total status of the job and add IshTranslationJobContainer objects that are eventually expanded by TranslationBuilder. After IshTranslationJob creation it should be possible to start the translation routine, triggering TranslationOrganizer activity.

• Add Add-IshTranslationJob
  • -Metadata can potentially handle ReadAccess and WriteAccess
  • -Container holds the topics and/or publications, so easiest way is to make this accept IshObject and generate the right xml structure
  • -XmlTranslationJobWorkflow as indicated by the Xml prefix, a raw passing of <translationjobworkflows><translationjobworkflow language="ru">Simple Workflow</translationjobworkflow></translationjobworkflows>
  • -TranslationJobWorkflow is theoretically a subset out of Add cmdlets *-IshTranslationTemplate #68. So one could dream up a subset selection out of Get-IshTranslationTemplate although tricky to stay within one template/alias
• Add Remove-IshTranslationJob
  • -Id as ParameterGroup
  • -IshObject as IshObjectGroup takes one or more jobs to remove
  • Perhaps a direct Remove parameter stating status and not-modified-since, so you can cleanup TranslationJobs with one cmdlet
• Add Set-IshTranslationJob
  • should at least allow the start/cancel of a TranslationJob... probably similar to Set-IshBaseline

Remarks...

• See Add read cmdlets *-IshTranslationJob and *-IshTranslationJobItem #69 on containers and ISHRemote.Format.ps1xml
• Remove-IshTranslationJobItem is not scope