• State Not Answered
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 64 views
  • Users 0 members are here
Options
Related

Retrieving a list of translation memories with GroupShareKit does not retrieve all translation memories

Daniel García Magariños

Dear all,

I am doing a basic test of the GroupShareKit and I created some simple code to retrieve a list of translation memories.

Here is the code:

var token = await GroupShareClient.GetRequestToken(GsUser, GsPassword, new Uri(strServerName), GroupShareClient.AllScopes);

GroupShareClient gsClient = await GroupShareClient.AuthenticateClient(token, GsUser, GsPassword, "", new Uri(strServerName), GroupShareClient.AllScopes);

var myTMs = await gsClient.TranslationMemories.GetTms();

The code is very simple and it runs without errors.

When I see the deails for the "myTMs" object, I see that it has 1037 items. Each item is a translation memory and and use the "locals" window in Visual Studio to see the TM properties (TMId, language pairs, etc.)

The problem is that in the server there are 1114 translation memories as shown from the GroupShare dashboard.

In both cases, I am logging in with the same user account. 

At some point, I can investigate which translation memories are not returned by GetTMs or if there is some limit but I wanted to ask here first in case somebody has seen a similar behaviour.

Or is this method paginated and I am just getting the first page or results?

Thanks!

Daniel
Rate translation
×
Suggest better translation
×
Parents
  • 0

    I think that the issue is not in the GroupShareKit but in the GroupShare Rest API itself.

    I have tested getting the translation memories with rest call using the swagger page from our own server and the number of translation memories obtained is the wrong one.

    curl -X GET --header 'Accept: application/json' --header 'Authorization: Bearer XXXYZ' 'OURSERVER/.../tms'

    I have seen which translation memories are not retrieved by the REST API but I cannot find any common pattern. The only thing I see is that there are 53 translation memories which are visible from the GroupShare dashboard and from the Studio interface but they are invisible for the GroupShare Rest API (and the GroupShare kit).

    Could it be that the GroupShare Rest  API is getting the translation memory details from some cached data? 

    The statistics widget in the GroupShare main page also shows the correct number of translation memories. The Studio API also retrieves the all the translation memories but it is slower.

    I wonder what might be going on... :?

    Daniel
Reply
  • 0

    I think that the issue is not in the GroupShareKit but in the GroupShare Rest API itself.

    I have tested getting the translation memories with rest call using the swagger page from our own server and the number of translation memories obtained is the wrong one.

    curl -X GET --header 'Accept: application/json' --header 'Authorization: Bearer XXXYZ' 'OURSERVER/.../tms'

    I have seen which translation memories are not retrieved by the REST API but I cannot find any common pattern. The only thing I see is that there are 53 translation memories which are visible from the GroupShare dashboard and from the Studio interface but they are invisible for the GroupShare Rest API (and the GroupShare kit).

    Could it be that the GroupShare Rest  API is getting the translation memory details from some cached data? 

    The statistics widget in the GroupShare main page also shows the correct number of translation memories. The Studio API also retrieves the all the translation memories but it is slower.

    I wonder what might be going on... :?

    Daniel
Children
No Data