# PMC install - inRiver Data Model Configuration
## Install - inRiver Data Model Configuration
### **inRiver PMC**
There are a number of things that needs to be configured in the Control Center(PMC).
* Go to the [inRiver Control Center](https://controlcenter.productmarketingcloud.com)
* Log in using your credentials
* Select a customer and an environment
* Navigate to
* Model
### CVL - Source Language
Languages in your PIM and translation languages are not necessary the same thing. That's why they need to be defined separately. In both language CVLs the following logic is applied; KEY=A unique key eg. "engb" VALUE=Language description eg. "English (Great Britain)"
The `sourceLanguages` are the possible language to translate from. Even if there only is one possible source language, a CVL with this language must be created.
* create a CVL called `sourceLanguages` with a list of the possible source languages to select from. Make sure to set the key as specified in the language configuration.
(sourceLanguages example)
### CVL - Target Languages
The `targetLanguages` are the possible languages to translate to. As with the sourceLanguages check these language lists with your Freeway set up.
* create a CVL called `targetLanguages` with a list of the possible target languages to select.
(targetLanguages example)
### CVL - Job Status
A translation job can have a number of status steps. They have to be defined in a CVL, this makes it easier for a user if the like to search for Jobs in a specific status.
* create a CVL called `trJobStatus`
| Key | Index | Value |
| ------------------ | ----- | ----------------------------- |
| Draft | 10 | Draft |
| Sending | 20 | Sending job |
| SendFailed | 25 | Error sending job |
| Sent | 30 | Job sent |
| InEvaluation | 40 | Job in evaluation |
| Cancelled | 50 | Job is cancelled |
| InProduction | 60 | Work in progress |
| ReadyForImport | 70 | Job ready for import |
| Imported | 80 | Imported |
| ImportedWithErrors | 85 | Imported but some with errors |
| Closed | 90 | Job done and closed |
### CVL - Job Actions
This CVL includes the actions that the user can make on Translation Jobs.
* create a CVL called trJobAction.
| Key | Index | Value |
| ------ | ----- | -------------------- |
| Send | 10 | Send for translation |
| Cancel | 30 | Request cancelation |
| Import | 40 | Import translation |
### CVL - Task Status
All translation tasks have a status.
* Create a CVL called `trTaskStatus.`
| Key | Sort Order | Value |
| ------------------ | ---------- | -------------------- |
| NotFound | 10 | Not translated |
| Ready | 20 | Ready for download |
| Imported | 30 | Imported |
| ImportedWithErrors | 40 | Imported with errors |
### CVL - Task Action
This CVL includes the actions that the connector can take on Translation Tasks.
* create a CVL called `trTaskAction`.
| Key | Sort Order | Value |
| ------ | ---------- | --------------- |
| Import | 10 | Import language |
### Entity - Translation Job
Create a new entity called `TranslationJob`, add the following required fields. (Find other fields in the Customization section). Source and Target languages are required to have default values if you run a automated work flow.
(Note that the image above shows the Display Name of the field type in the `Name` column, and not the Id)
1. `trJobId`: The FreewayID of the Job, Read Only
2. `trJobName`: Your name of the Job, Mandatory
3. `trSpecialInstructions`: Special instructions for translation
4. `trPOReference` : Your P.O reference
5. `trExpectedDeliveryDate` : When you expect delivery, Mandatory
6. `trAutomated`: boolean : If the Job process is automated (Not to be set manually)
7. `trSourceLanguage`: CVL, sourceLanguages : Translate from, Mandatory
8. `trTargetLanguages`: CVL, targetLanguages: Translate to, Manatory, Multivalue
9. `trJobStatus`: CVL, trJobStatus : PIM and Freeway status of the Job, Read Only, Default value `Draft`
10. `trJobAction`: CVL, trJobAction Actions to take on the Job (If manual),
### Entity - Translation Task
Create a new entity called `TranslationTask`, add the following required fields.
(Note that the image above shows the Display Name of the field type in the `Name` column, and not the Id)
1. `trTaskId`: FreewayID of the task, Read Only.
2. `trTaskName`: Language Source-Target, Display Name, Read Only.
3. `trTaskSourceLanguage`: String, Read Only.
4. `trTaskTargetLanguage`: String, Read Only.
5. `trTaskStatus`: CVL, trTaskStatus : Status of the Task, Display Description, Read Only, Default value `NotFound`.
6. `trTaskAction`: CVL, trTaskAction : Action to take on the Task
### Modify Existing Entities
On the entities that you will translate you need to add three fields.
| Field Type Id | Data Type | CVL | Multivalue | Read Only | Hidden | Track Changes |
| --------------------------------- | --------- | --------------- | ---------- | --------- | ------ | ------------- |
| `tr[EntityType]InTranslation` | CVL | targetLanguages | Yes | Yes | No | Yes |
| `tr[EntityType]Translated` | CVL | targetLanguages | Yes | Yes | No | Yes |
| `tr[EntityType]TranslationStatus` | Xml | | No | Yes | Yes | Yes |
### Add links
All the entities that you should translate need a link to the Job.
* Add links between Translation Job and the entities you like to translate. E.g. Translation Job -> Product
* And all other Entities that you like to be able to add to a Translation job
* Add the following required links
| Link type id | Source entity type | Target entity type | Suggested inbound name | Suggested outbound name |
| ----------------------------- | ------------------ | ------------------ | ---------------------- | ----------------------- |
| TranslationJobTranslationTask | TranslationJob | TranslationTask | Translation Tasks | Translation Job |
| TranslationJobTranslationJob | TranslationJob | TranslationJob | Translation Job Batch | Translation Job Batch |
| TranslationTaskResource | TranslationTask | Resource | Files to translate | Translation Task |
### Server Configuration
For users to be able to create Translation Jobs you must add that entity to the list of creatable entities.
* Add `TranslationJob` to the "DEFAULT\_CREATE\_ENTITIES" setting in System Settings.
* **Don't forget the comma separator!**
### **ICONS**
To have customised icons displayed for connector Translation Jobs(
) and Translation Tasks(
) select these enity types in the Model section and click the Upload icon button.
Translation Jobs will display like this:
Translation Tasks will diplay like this:
