COTI is an exchange standard for CMS systems, that want to send data to translation processes.
COTI has 3 levels, level 2 is a hotfolder-like exchange.
Goal of this issue is to implement COTI level 2 support for translate5.
The spec can be found here: https://www.dercom.de/en/projekte
Implementation as new Plugin, similar to the already existing Hotfolder solution.
COTI Example XML - WORK IN PROGRESS
- add a switch to decide if each COTI/Project in COTI/Package maps to translate5/Task with type default or COTI/Package maps to Translate5/Project and each COTI/Project to a translate5/task of that Project.
Any way we should import each Coti/Project as single tasks and do not make any bulk project to task import here.
The following example file is from the spec documentation. Please check the XSD file also from above URL to validate mandatory and optional fields:
<coti version="1.0" level="1" creator="DERCOM" creation-date="2013-08-21T12:00:00Z" package-id="" xmlns="http:<project
name="COTI-Description" โ concat to translate5 task name
project-id="4711" โ task foreign id
proposal="yes" โ no relation in translate5
checkout-date="2013-08-21T11:59:00Z"
due-date="2013-09-10T00:00:00Z"
comment="very urgent!"
tms-id="">
<subject>Subject</subject>
<meta name="CMS meta field" value="123" description=""/>
<translation
name="Project00345"
source-language="de-DE"
target-language="en-GB"
status="final">
<translation-file
file-ref="translation files/chapter1.xml"
mime-type="text/xml"
encoding="UTF-8"
creation-date="2013-05-17T11:59:00+01:00"
content-id=""
type=""
target-encoding=""
tms-id=""/>
<reference-file
external="yes"
type="other"
file-ref="reference files/chapter1.pdf"
mime-type="application/pdf"
encoding=""
description="Preview PDF"
tms-id=""/>
</translation>
</project>
</coti>