SOAP API TM lookups not returning correct results

Hi,

We are trying to do some TM look ups using the SOAP API and are getting some odd results. 

For example when we are calling exactLookupByTarget_ with information for the TM, search text, source and target we will often get back a blank array "[ ]" for searches we can confirm in the UI that have 100% matches. Then when we perform the same search using the more general lookupByTarget_ we get results but with match scores that do not make much sense.

Is there a way to force these calls to behave closer to the UI search matching? 

For example on a call searching for "Beschreibung" in the target German for the call "lookupByTarget_(token=Token, wSTm=TMName, searchText='Beschreibung', sourceLanguage='English (United States)', targetLanguage='German (Germany)')" along with a lot of other information we get:

[{'token': '*************', 'id': None, 'displayString': None, 'target': 'Beschreibung', "rawTarget': 'Beschreibung',
'source': 'Description',
'tmDatabaseId': ####,
'score': 25.0,
'isRepaired': False,
'rawSource': 'Description',
'isReversedHit': False}

and the call with the same TM and search information for exactLookupByTarget_ returns:

[]

What I can't tell is why 1. the match score is only 25.0 on the look up call and why the text being exact does not register over the SOAP call.

Any advice on how to resolve would be appreciated. 

  • Hi Joseph,

     

    The SOAP call lookupSubstringByTarget_ can be used to get similar results with the UI (the results for Translation Memory search page): search type standard, search in target, minimum score equal with the one returned in UI.

    Example of the parameters:

           <token xsi:type="xsd:string">********** </token>

            <wSTm xsi:type="xsd:string">Anca_test</wSTm>

            <searchText xsi:type="xsd:string">Genauigkeit</searchText>

            <sourceLanguage xsi:type="xsd:string">English (United Kingdom)</sourceLanguage>

            <targetLanguage xsi:type="xsd:string">German (Germany)</targetLanguage>

            <minimumScore xsi:type="xsd:double">25</minimumScore>

     

    Please try it out and let me know if this works for you.

     

    Thank you,

    Anca 

  • Hi Anca,

    Thank you for your help. It does seem like this is returning more accurate results that are closer to what we would see from the UI lookups.

    We will test out and see if we have any other issues but this solves the main problem at least!

    Best,

    Joe