I just stumbled across a problem in the translations endpoint for collection (and also saw one missing thing). I tried the following things with the collection "Asterix and Obelix (Animation) Collection / 94039"

1. when calling the collections details with any language which is not translated, I get the "default" title of the collection (which is probably EN in this case, but the API offers absolutely NO information about the language the title is in). Just call the endpoint with the language Indonesian (ID) and the collection.name is filled (but with EN) and the overview is empty. But when looking at the translation endpoint for that collection, you see that neither the name nor the overview is translated into EN, which shows me that there is some sort of fallback in the API itself. Which leads to point 2:

2. when calling the translation service of the collection, I do not see any title translation for EN, but an overview translation. As I saw in the request before, I know that there is an English translation! Let us construct an example: our user understands Indonesian, English and Fench, so he wants the title either in Indonesian or English or French. Calling this API for ID, returns the collection name in

3. collection.name = EN

4. translations: ID = empty, EN = empty, FR = filled

Since I do not know that collection.name is in EN (and not DE for example) I must use the collection.name in FR since this is the only translation I am sure about.

Due to the combination of this two behaviors it is almost impossible to fetch the correct translations for our users, since I never know which part is translated and which not (but injected by the API with default values!). This also leads to my request

1. please also add the append_to_response for collection images AND collection translation to help up avoiding unnecessary requests!