Specialization mapping has two views, the Grid view and the Rule-based view. The Rule-based view is an exception-based selector, the Grid view is a value mapping selector. You can switch between the two views using the radio button in the top right corner.
In the Grid view, the right side shows the list of specializations coming from your business management system (BMS), and the left shows you the list from the origin system.
XTRF/Protemos: both of these systems have a list of specialization values.
Plunet: it comes from the specialization property you defined during setting up your Plunet connection.
REST API: the specialization values are uploaded by you.
Specialization’s main use is to help you select the right translators and their correct price lists in case you have an automated vendor selection in your BMS.
First, click on any empty line on the left side. The left side (origin system) includes a drop-down list with all the unmapped specialization values. You need to map them all to the corresponding BMS value on the right side. As you move forward with this mapping, you might notice that some values were already mapped by BeLazy. If they are in the correct value, you don't need to re-map them. If you want to map them to a different specialization, you can unmap that value by unchecking the checkbox and looking for the correct value on the right side, and selecting the specialization from the drop-down list next to it.
Values already mapped will disappear from the drop-down list.
Depending on the origin system, specialization can have different names such as Domain, Subdomain, Content type, etc.
If, for some reason, in your BMS, you always use the same Specialization for the projects that come from the connection you are setting up, you can map all specialization values from the origin system into one value in your BMS. For example: General
The Rule-based view allows you to set up a default specialization value and exceptions based on other metadata. Use this view if the system sending you projects does not give a specialization value, or it is not correct or detailed enough, and you would like to bind specialization to the metadata values in other fields.