Page tree
Skip to end of metadata
Go to start of metadata

If the API changes in an incompatible manner this is listed explicitly in the "important release notes" section of each releases changelog.

URL:

/editor/plugins_matchanalysis_matchanalysis/?taskGuid="your task guid here"

Available Methods:

GET listing only

Specialities:

Returns a list of words count in a matchrate group for each associated language resource. Each segment can only appear in one matchrate and language resources group.

Availability:

public

Match analysis Export URLs

URL to get the match analysis results exported:

export

Parameter types"excel", xml


Response Layout

Name

Type

Info

resourceName

string

GET only

resourceColorstringGET only
createddateGET only
internalFuzzybooleanGET only
104numberGET only, match from term collection
103numberGET only, context match
102numberGET only, repetition
101numberGET only, exact-exact match
100numberGET only
99numberGET only, matches with matchrate between 90 and 99
89numberGET only, GET only, matches with matchrate between 80 and 89
79numberGET only, matches with matchrate between 70 and 79
69numberGET only, matches with matchrate between 60 and 69
noMatchnumberGET only, matches with matchrate between 0 and 59

Injected task operation to start the analysis and or pre-translation

The analysis / pre-translation of a task is started via the following two operations on a specific task.

URL:

/editor/task/TASK_ID/analysis/operation


Available Methods:

PUT only


Purpose:Starts the analysis of a task

Parameters:

internalFuzzy

0 or 1 if internal fuzzies should be used or not
Availability:

public



URL:

/editor/task/TASK_ID/pretranslation/operation


Available Methods:

PUT only


Purpose:Starts the analysis and pre-translation of a task

Parameters:

internalFuzzy

0 or 1 if internal fuzzies should be used

pretranslateMatchratenumber between 0 and 100, the minimum matchrate of a found TM match to be considered as a valid pre-translation

pretranslateTmAndTerm0 or 1, defines if TMs and Term Collections should be used for pre-translation

pretranslateMt0 or 1, only usable if above pretranslateTmAndTerm is used, defines if MTs should be used also for pre-translation if no usable TM / Term was found

termtaggerSegment0 or 1 if terminology should be marked if a term collection is assigned as well, currently only usable on import

isTaskImport0 or 1 defines if call is in import or not, will be removed in the future, since can be loaded from the task as well, only needed when using termtaggerSegment
Availability:

public


  • No labels