EDIT

I will do the review after the release as I have no test data on test

Test data: http://int.e-taxonomy.eu/dataportal/integration/reference/cdm_dataportal/taxon/d245083e-3bda-435f-9bb3-bdc2249ff23c/specimens

The example data look ok, but not fully similar to the reported data structure from production. Therefore I suggest to keep the ticket open for a final check with production though I don't expect problems.

Andreas Kohlbecker wrote:

I don't understand why you are changing the category, this clearly was a bug in cdmlib-services

Definetely "cdm" was wrong as "cdm" is for model related issues only. Therefore I was changing the category.

I also thought about changing to cdmlib instead of dataportal. I think we do not have a clear distinction for this. We often assign issues to dataportal or taxeditor though the reason for the bug is somewhere in cdmlib. Especially if cdmlib code is used primarily by one application.
In these cases it is easier to write the Roadmap for the release because for the users it is definetly more interesting to know that a bug was fixed in dataportal then in cdmlib (as cdmlib is something abstract for them).

However, if you think we should assign it to cdmlib feel free to do so.