Details
-
Bug
-
Resolution: Won't Fix
-
Major - P3
-
None
-
*Location*: https://docs.mongodb.org/manual/applications/data-models-tree-structures/
*User-Agent*: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36
*Referrer*: https://docs.mongodb.org/manual/core/data-model-design/
*Screen Resolution*: 1920 x 1080
*repo*: docs
*source*: applications/data-models-tree-structures
*Location*: https://docs.mongodb.org/manual/applications/data-models-tree-structures/ *User-Agent*: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.80 Safari/537.36 *Referrer*: https://docs.mongodb.org/manual/core/data-model-design/ *Screen Resolution*: 1920 x 1080 *repo*: docs *source*: applications/data-models-tree-structures
-
0.25
Description
My 2c as a beginner on this material...
Change the example scenario to be something unrelated to what is being learned. By that I mean instead of a tree with nodes that happen to relate to what is being learned... "MongoDB", "Databases", choose something completely unrelated. I would suggest "United States", "California", "San Francisco". That is better for two reasons. 1. A novice will not be confused when seeing "MongoDB" is quotes and wondering if that is a call or something related to the function of the database. 2. Users know the natural hierarchy of country-state-city. When looking through the json document, they don't need to refer back to the document, and say, oh yeah, "Programming" is a child of "Books" (not a natural relationship they would immediately know). It makes it faster to grok what is going on when comparing the json documents. 2b. Don't choose a node name that is plural. "Databases" may confuse the novice that it is itself referring to something that has an array of multiple instances, rather than just being a singleton string. That is my 2c as someone coming from RDBMS side...