# Add the library name as the first part of hierarchic structure

**URL:** <https://community.qonic.com/t/add-the-library-name-as-the-first-part-of-hierarchic-structure/222>\
**Category:** Feature Requests\
**Created:** [August 25, 2025, 7:45am UTC](https://community.qonic.com/t/add-the-library-name-as-the-first-part-of-hierarchic-structure/222 "2025-08-25T07:45:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Johan\_De\_Cock](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.qonic.com/johan_de_cock/32/235_2.png) [@Johan\_De\_Cock](https://community.qonic.com/u/Johan_De_Cock)\
**Post date:** [August 25, 2025, 7:45am UTC](https://community.qonic.com/t/add-the-library-name-as-the-first-part-of-hierarchic-structure/222/1 "2025-08-25T07:45:14Z")

</div>

In a model where multiple codification standards are applicable (like the attached example with Uniformat imported from the IFC/RVT and a custom library added), the results are not grouped per library or codification system.

I’d expect the hierarchical structure to start with “Uniformat” and “Custom library name” as in the second screenshot. Then go into the codes.

 ![image](https://canada1.discourse-cdn.com/flex011/uploads/qonic/original/1X/bc7234c19c8cc69a4778ce30a380d3ebcb5a3bdc.png)

 ![image](https://canada1.discourse-cdn.com/flex011/uploads/qonic/original/1X/d8c682bd0eb217c434a373eade98a94c7917d6f8.png)

---

<div class="post-metadata">

**Author:** ![Dieter](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.qonic.com/dieter/32/106_2.png) [@Dieter](https://community.qonic.com/u/Dieter)\
**Post date:** [August 25, 2025, 10:35am UTC](https://community.qonic.com/t/add-the-library-name-as-the-first-part-of-hierarchic-structure/222/2 "2025-08-25T10:35:50Z")

</div>

Good point Johan, thx. We’ll add that to the browse panel.