# Small category tree anomalies

**URL:** <https://dbnomics.discourse.group/t/small-category-tree-anomalies/972>\
**Category:** Data Issues\
**Created:** [September 12, 2025, 4:44pm UTC](https://dbnomics.discourse.group/t/small-category-tree-anomalies/972 "2025-09-12T16:44:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![acottrell](https://avatars.discourse-cdn.com/v4/letter/a/c68b51/32.png) [@acottrell](https://dbnomics.discourse.group/u/acottrell)\
**Post date:** [September 12, 2025, 4:44pm UTC](https://dbnomics.discourse.group/t/small-category-tree-anomalies/972/1 "2025-09-12T16:44:38Z")

</div>

Thanks for all your good work; dbnomics becomes ever more comprehensive.

Working on the dbnomics client for gretl I came across a few anomalies in the category trees for certain providers, which make life a bit more difficult than it needs to be for authors of client programs.

- Almost all datasets have both a code and a name, but the OECD dataset with code “REGION\_ECONOM” has a JSON null value in place of a name.
- In the tree for the Bank for International Settlements, many “name” fields have a string of the expected sort, but with a newline character and a chunk of whitespace appended.

In both of these cases some additional work is needed to make the “name” usable in third-party code.