Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Model a small domain (e.g. a blog or product catalog) as MongoDB documents and load it with mongosh. Decide embedding vs referencing deliberately (e.g. embed comments in a post, reference an author) and justify it. Insert with insertMany, then write queries using operators ($in, $gt, dot-notation on nested fields, an array match) with projections, and produce two small reports with an aggregation pipeline ($match + $group). Keep documents under the 16 MB limit and avoid unbounded arrays.
Embedding vs referencing chosen deliberately and justified by access patterns; no unbounded arrays / oversized docs.
Correct query operators, dot-notation on nested fields, array matches, and projections.
At least two pipelines using $match + $group (with accumulators) that produce correct results.
Runs in mongosh; documents are well-formed; _id usage correct.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# A document-modeled catalog ## Goal Model a small domain (e.g. a blog or product catalog) as MongoDB documents and load it with mongosh. Decide embedding vs referencing deliberately (e.g. embed comments in a post, reference an author) and justify it. Insert with insertMany, then write queries using operators ($in, $gt, dot-notation on nested fields, an array match) with projections, and produce two small reports with an aggregation pipeline ($match + $group). Keep documents under the 16 MB limit and avoid unbounded arrays. ## Acceptance criteria - [ ] Document modeling: Embedding vs referencing chosen deliberately and justified by access patterns; no unbounded arrays / oversized docs. - [ ] Querying: Correct query operators, dot-notation on nested fields, array matches, and projections. - [ ] Aggregation: At least two pipelines using $match + $group (with accumulators) that produce correct results. - [ ] Correctness: Runs in mongosh; documents are well-formed; _id usage correct. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.