# The Issue between String to Document and NGram Creator (v.4.2.3)

**URL:** <https://forum.knime.com/t/the-issue-between-string-to-document-and-ngram-creator-v-4-2-3/30796>\
**Category:** KNIME Extensions\
**Tags:** text-processing\
**Created:** [February 19, 2021, 8:05pm UTC](https://forum.knime.com/t/the-issue-between-string-to-document-and-ngram-creator-v-4-2-3/30796 "2021-02-19T20:05:16Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![izaychik63](https://forum-cdn.knime.com/letter_avatar_proxy/v4/letter/i/e9a140/32.png) [@izaychik63](https://forum.knime.com/u/izaychik63)\
**Post date:** [February 24, 2021, 8:56pm UTC](https://forum.knime.com/t/the-issue-between-string-to-document-and-ngram-creator-v-4-2-3/30796/2 "2021-02-24T20:56:39Z")

</div>

I found this explanation from @ScottF

> [@(Urgent) I am having some problem with Strings to document node](https://forum.knime.com/t/urgent-i-am-having-some-problem-with-strings-to-document-node/18047/5):
>
> So far I have been able to increase the accuracy to just under 95% by using default XGBoost instead of the Decision Tree. I am doing some simple parameter optimization now that will hopefully improve results further - when it completes, I’ll post the updated workflow. What is your accuracy goal for this task? Or are you using some other model quality metric?

Anyway, the fact that title is included in the corpus needs to be addressed. I use the title as a key. Also, it looks like title considered as separate document (???).

---

_[View the full topic](https://forum.knime.com/t/the-issue-between-string-to-document-and-ngram-creator-v-4-2-3/30796)._