# Doccommentdata node (Document Commenting Plugin) categorization

**URL:** <https://community.bloomreach.com/t/doccommentdata-node-document-commenting-plugin-categorization/455>\
**Category:** Experience Manager (PaaS/OnPrem)\
**Created:** [September 28, 2018, 12:20pm UTC](https://community.bloomreach.com/t/doccommentdata-node-document-commenting-plugin-categorization/455 "2018-09-28T12:20:34Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Davey\_Chu](https://avatars.discourse-cdn.com/v4/letter/d/ecd19e/32.png) [@Davey\_Chu](https://community.bloomreach.com/u/Davey_Chu)\
**Post date:** [September 28, 2018, 12:20pm UTC](https://community.bloomreach.com/t/doccommentdata-node-document-commenting-plugin-categorization/455/1 "2018-09-28T12:20:34Z")

</div>

Hello community,

We are migrating from Hippo 11 to 12 and have used the Document Commenting Plugin for quite some time. The doccommentdata node’s children seem to contain the current comments. As far as I can tell, the latest (3.0.0) version of the plug-in does not explicitly categorize child-nodes (through .meta:residual-child-node-category) so they default to config. This results in the doccommentdata being wiped out (as the Configuration Verifier correctly detects).

My question: Is this intended behavior? If not, should the child nodes be categorized as content or system?

Kind regards,  
Davey Chu

---

<div class="post-metadata">

**Author:** ![woonsanko](https://avatars.discourse-cdn.com/v4/letter/w/b5a626/32.png) [@woonsanko](https://community.bloomreach.com/u/woonsanko)\
**Post date:** [September 28, 2018, 12:53pm UTC](https://community.bloomreach.com/t/doccommentdata-node-document-commenting-plugin-categorization/455/2 "2018-09-28T12:53:22Z")

</div>

Hi Davey,

> [@Davey\_Chu](#):
>
> My question: Is this intended behavior? If not, should the child nodes be categorized as content or system?

I think you’re right. Would you provide a pull request against the develop branch [1]? Then we’ll do the next step soon.

Woonsan

[1] [GitHub - bloomreach-forge/document-commenting: Add commenting functionality for content editors in the CMS](https://github.com/onehippo-forge/document-commenting)

---

<div class="post-metadata">

**Author:** ![Davey\_Chu](https://avatars.discourse-cdn.com/v4/letter/d/ecd19e/32.png) [@Davey\_Chu](https://community.bloomreach.com/u/Davey_Chu)\
**Post date:** [September 28, 2018, 1:29pm UTC](https://community.bloomreach.com/t/doccommentdata-node-document-commenting-plugin-categorization/455/3 "2018-09-28T13:29:48Z")

</div>

Hi Woonsan,

I have made a pull request that categorizes the child nodes as content. If they are better categorized as system, I’ll gladly change it. For my own understanding, I would appreciate it if you could explain your reasoning for one or the other category.

Kind regards,  
Davey Chu

---

<div class="post-metadata">

**Author:** ![woonsanko](https://avatars.discourse-cdn.com/v4/letter/w/b5a626/32.png) [@woonsanko](https://community.bloomreach.com/u/woonsanko)\
**Post date:** [September 28, 2018, 5:29pm UTC](https://community.bloomreach.com/t/doccommentdata-node-document-commenting-plugin-categorization/455/4 "2018-09-28T17:29:35Z")

</div>

Hey Davey,

Thanks again! You’re totally right. Would you change it to “system”? Then I will merge it and cut a new release very soon.

The /doccommentdata node is the comment data storage folder, similarly to HST Form Data storage [2,3]. And HST also sets it to “system”. [4]

Woonsan

[2] [https://www.onehippo.org/library/concepts/component-development/hst-2-forms.html](https://www.onehippo.org/library/concepts/component-development/hst-2-forms.html)  
[3] [https://www.onehippo.org/library/administration/maintenance/form-data-cleanup.html](https://www.onehippo.org/library/administration/maintenance/form-data-cleanup.html)  
[4] [https://code.onehippo.org/cms-community/hippo-site-toolkit/blob/hst-5.4.0/toolkit-resources/addon/repository/src/main/resources/hcm-config/formdata.yaml#L4](https://code.onehippo.org/cms-community/hippo-site-toolkit/blob/hst-5.4.0/toolkit-resources/addon/repository/src/main/resources/hcm-config/formdata.yaml#L4)

---

<div class="post-metadata">

**Author:** ![Davey\_Chu](https://avatars.discourse-cdn.com/v4/letter/d/ecd19e/32.png) [@Davey\_Chu](https://community.bloomreach.com/u/Davey_Chu)\
**Post date:** [September 30, 2018, 9:00am UTC](https://community.bloomreach.com/t/doccommentdata-node-document-commenting-plugin-categorization/455/5 "2018-09-30T09:00:11Z")

</div>

Hi Woonsan,

I updated the pull request. Thanks for the extra explanation.

Kind regards,  
Davey Chu

---

<div class="post-metadata">

**Author:** ![woonsanko](https://avatars.discourse-cdn.com/v4/letter/w/b5a626/32.png) [@woonsanko](https://community.bloomreach.com/u/woonsanko)\
**Post date:** [October 1, 2018, 2:44am UTC](https://community.bloomreach.com/t/doccommentdata-node-document-commenting-plugin-categorization/455/6 "2018-10-01T02:44:58Z")

</div>

Thanks again for your contribution, Davey!  
I’ve cut a new release, v3.0.1:

- [https://onehippo-forge.github.io/document-commenting/release-notes.html](https://onehippo-forge.github.io/document-commenting/release-notes.html)

Cheers,

Woonsan
