Using Article Type Extraction

The Article Type Extraction functionality allows you to quickly and easily define the scope of your translations for the Language I/O Article plugin.

Prerequisites

You must set up the Article Type Extraction functionality before you can use it. 

Extracting the data

1. From the App Launcher, find the tab that you created during setup. In this example, the label of the tab is Extract Knowledge Data:
   
   
2. The tab opens. Click on the Extract Knowledge Data button at the center to start the download:
   
3. Depending on the settings of your browser, you might get a prompt to specify a folder, or your browser might download the file directly into your Downloads folder. The file is in CSV format.

Defining the scope of your translations

1. Locate the downloaded CSV file and open it in a spreadsheet program, for example MS Excel.
2. If the file is not formatted automatically, you must do it before you can proceed. Here is how you can format a CSV file in MS Excel:
   1. Type "Ctrl+A" to select all the contents of the CSV file.
      
   2. Go to the Data tab and click on Text to columns:
      
   3. Select Delimited and click Next.
   4. Select Comma and click Next.
   5. Click Finish. You can now see that the data in the file is divided into eight columns:
      
3. You can now edit the file to set the scope of your translations:
   1. Record Type
      • Do not modify anything in this column.
   2. Field Label
      • Do not modify anything in this column.
   3. Field Name
      • Do not modify anything in this column.
   4. Field Type
      • Do not modify anything in this column.
   5. To be Translated?
      • Fill in each row with "Yes" or "No".
   6. Include in Translated Article?
      • Fill in each row with "Yes" or "No", depending on whether you want the field to appear in the translated article.
      • If you defined To be Translated as "Yes", then you must set this field to "Yes", but you can include other fields as well (for example, dates or URLs)
      • If a value is already pre-filled, do not modify it.
   7. Required (Is there a field validation that prevents an article draft from being saved if the field is missing?)
      • Fill in each row with "Yes" or "No", depending on whether the field is required. 
      • If a value is already pre-filled, do not modify it.
   8. Editable (Can a user edit this field after the article is created)
      • Fill in each row with "Yes" or "No".
      • If you defined To be Translated as "Yes", then you must set this field to "Yes".
4. Once you finish, save the file and send it to your Language I/O Customer Success Manager so that they can configure your Language I/O tool.