Import extension language or dialect terms (via a batch upload)
Steps
References
From the Dashboard - My Tasks view, press Upload a Batch in the left-hand menu bar.
Content translation terms are imported via .tsv (tab-separated values) text files, with three format types corresponding to the following actions:
Description Additions
Description Changes
The Upload a Batch pop-up form is presented, centred on the page and overlaying the Dashboard - My Tasks view which is dimmed but still visible "below" the form.
This form has the following fields and calls to action:
Task Title (single line text entry, freely editable)
Select Project (drop-down select list of projects available to the authenticated author)
Description Inactivations
See for some examples of these files, including sample download .tsv files.
Select Assignee (drop-down select list of all registered AP accounts)
Select Reviewer (drop-down select list of all registered AP accounts)
Number of Concepts Per Task (drop-down select list)
Select Import Type (drop-down select list; must match the upload file format)
Select Batch File (opens the browser's local file selector dialogue to specify a batch file for upload)
Create Tasks (inactive until a batch .tsv file is uploaded)
Cancel (closes the pop-up form without making any changes)
When all fields are defined, the Create Tasks button is enabled - press the button to upload the batch file start the import process.The imported changes are allocated to new tasks according to the number of change rows and the maximum number of concepts per task defined on the form, which has the following options: _5, 10, 15, 20, 15, 50, 100 (default), 200, 500.
So, for instance if the source file contains 41 rows, and the number of concepts per task is set to 15, then 3 new tasks will be created, with the last one containing 11 changes, and the others 15 each.
The default option of 100 is chosen so that most use cases only need one new task, but a smaller number may make it easier to review changes.
If multiple tasks are created they are identified by reference numbers which are automatically suffixed to the Task Title.
Following upload and processing of the batch file, successful complete of processing is indicated via a header notification for "All tasks loaded", newly created task(s) in the My Tasks listing, and a browser download .tsv file which contains the import result for each processed row from the uploaded batch source file.
The example below shows a success result file for 3 description additions to existing published International concepts, adding Maori language translations in the New Zealand (NZ) extension:
Following successful import, the changes made can be seen in the Authoring Platform by opening each related import task.
On first opening the task, the edit panel will be empty, since no manual editing has occurred.
Use the Switch to Feedback View context tab to see each modified concept in the To Review list.
Loading the modified concepts into the Review Panel highlights their changes, in exactly the same way as those made manually via regular editing.
The example shown here shows two NZ extension description changes made via batch import.
Another example showing two NZ extension description inactivations made via batch import.
Another example showing three Maori translated terms added to existing International published concepts, with the new descriptions added to the NZ extension module.
(Google translations of en-US terms into Maori are for illustration purposes only!)
Google sheets can be used to quickly generate .tsv files from a worksheet tab, via its File > Download > Tab separated values (current sheet) menu function. Google sheets also offers useful file sharing and commenting options, so can be an efficient approach to defining, reviewing, and refining extension translation terms prior to importing into the Authoring Platform.
Here are some example .tsv translations (New Zealand) batch upload files:
Description Additions
Concept ID
GB/US FSN Term (For reference only)
Translated Term
Language Code
Case significance
Type
Language reference set
Acceptability
Language reference set
Acceptability
Language reference set
Acceptability
Reference file:
Description ID
Term (For reference only)
Case significance
Type
Language reference set
Acceptability
Language reference set
Acceptability
Language reference set
Acceptability
Reference file:
Description ID
Term (For reference only)
Inactivation Reason
Association Target ID1
Association Target ID2
Association Target ID3
Association Target ID4
Reference file:
706689003
Application programme software (physical object)
He raupaparorohiko raupaparorohiko
mi
cI
SYNONYM
Maori
PREFERRED
442376007
Test with result pending (observable entity)
Whakamatau me te hua ka tatari
mi
cI
SYNONYM
Maori
PREFERRED
70056012
Insertion of catheter into heart chamber
cI
SYNONYM
NZ English
ACCEPTABLE
US English
ACCEPTABLE
GB English
ACCEPTABLE
3658267015
Inflammatory disorder due to increased blood urate level
ci
SYNONYM
NZ English
PREFERRED
US English
ACCEPTABLE
GB English
ACCEPTABLE
150085018
Gout
CS
SYNONYM
NZ English
ACCEPTABLE
US English
PREFERRED
GB English
PREFERRED
51631000210119
Screening for diabetes mellitus during pregnancy
Outdated
706690007
Web-based application software (physical object)
Me tono rorohiko-a-paetukutuku
mi
cI
SYNONYM
Maori
PREFERRED
51691000210118
GDM-Gestational diabetes mellitus screening
Description Changes
Description Inactivations
Google sheets for batch upload file creation and editing
