Digital Asset Catalogue with MongoDB: A 2027 Project Guide

A convincing MongoDB portfolio project explains the result as well as showing it. Here, a student design-team coordinator asks: How much approved asset data is listed in each category? You will build a document model and aggregation and follow the relevant records from a small fixture to an independently checked answer.

This is a 2027 study-edition project brief. All example records and operational situations are fictional. Start with basic MongoDB knowledge, the ability to inspect structured data and a local practice environment. The complete first version should answer the stated question before adding accounts, real integrations or additional screens.

Define the project rule

Approved asset size is a storage-planning measure. Use one documented unit convention; do not mix decimal kilobytes and binary kibibytes in the same field. For this exercise, one row represents one asset. The stable key is record_id; asset_category is the grouping or filtering label. The numeric size_kb field uses kilobytes. Accepted states are draft, approved, archived.

The summary selects status approved and applies sum to the selected numeric values. Keep this definition visible in the interface, response or report so another learner can reproduce it. Use positive finite values in the starter fixture and define any future zero or missing-value policy explicitly.

Choose the MongoDB approach

Design a document around the operations the project needs. Decide what is embedded, what is referenced and which identifier remains stable. Validate a small set of representative documents before writing an aggregation. Avoid turning every relationship into an unbounded array. Test the pipeline stage by stage so a filter or unwind does not silently change the grain.

The three design decisions to explain in your project notes are:

• Document boundaries. Apply this choice to asset records and explain its effect on size_kb.
• Schema validation. Apply this choice to asset records and explain its effect on size_kb.
• Aggregation-stage reconciliation. Apply this choice to asset records and explain its effect on size_kb.

Work through a small sample

The three records below are deliberately small enough to inspect by hand. They are a compact specification for the data shape and expected result, and can later be expanded into a larger synthetic fixture.

[
  {
    "record_id": "asset-catalogue-01",
    "asset_category": "Course Banner",
    "size_kb": 320,
    "status": "approved",
    "recorded_on": "2027-01-04"
  },
  {
    "record_id": "asset-catalogue-02",
    "asset_category": "UI Icon",
    "size_kb": 480,
    "status": "draft",
    "recorded_on": "2027-01-05"
  },
  {
    "record_id": "asset-catalogue-03",
    "asset_category": "Project Screenshot",
    "size_kb": 160,
    "status": "approved",
    "recorded_on": "2027-01-06"
  }
]

Only the first and third records match approved. Their size_kb values are 320 and 160; the full-fixture result is 480 kilobytes, with 2 matching records. Selecting asset_category = Course Banner leaves the first record, so the result becomes 320 kilobytes, with 1 match. This provides two independent checks for the filter and aggregation.

The full-fixture output contract is:

{
  "matching_count": 2,
  "operation": "sum",
  "value": 480,
  "unit": "kilobytes"
}

Check the result by asset_category

The overall figure answers the all-records version of the question. Grouping by asset_category produces the following separate expectations, using the same approved rule. The middle group has a record in the source fixture but no qualifying observation.

Use this breakdown when answering the group-level question. Compare like-for-like units and keep the matching count visible, especially for averages. A different filter changes which records enter the calculation; it does not change the meaning of the metric.

The code blocks describe sample data and an expected result. Implement the surrounding feature using the installed version of your chosen tools, then save the actual run evidence separately from these expectations.

Build the feature in three passes

1. Define identity and row grain

One record represents one asset, not one asset_category label. Give record_id a uniqueness constraint and describe the allowed status values. Model size_kb as a numeric quantity with a documented kilobytes unit rather than an arbitrary string.

2. Write the filtered aggregation

Filter to status approved before applying the sum to size_kb. Add a asset_category filter as a separate condition. Inspect the matching records before grouping; this exposes duplicate rows and incorrect joins that an attractive total can conceal.

3. Check changes and reconciliation

Try a valid update and a rejected invalid record, then rerun the summary. Compare source-row counts with the aggregate input. Explain what an absent field, an empty group and a repeated identifier mean in the chosen storage design.

Find the mistake before polishing the result

A useful defect to introduce deliberately is: A mixture of bytes and kilobytes produces a plausible but incorrect total. First reproduce it against the fixture, then identify the smallest rule or state transition that explains the mismatch. Fix that boundary and rerun the full-fixture and selected-label examples. This creates a stronger explanation than changing several unrelated parts until the screen looks right.

The scenario-specific acceptance check is: Normalize the fixture to one declared unit before aggregation. Preserve before-and-after evidence. Add a missing asset_category, a negative size_kb, an unrecognised status and a duplicate record_id as separate invalid cases. Define the rejection or duplicate-handling policy before testing, and verify that invalid input does not silently change valid existing records.

Check the MongoDB concerns as well:

• An update must target the intended document.
• An aggregation must not double count array elements.
• An absent field must have a documented meaning.

For an empty filter match, the expected sum value is 0. Keep matching_count at zero. This distinction prevents an empty dataset from being interpreted as a measured observation.

Explain the finished work in a portfolio

Show the student design-team coordinator question, the record definition and the expected calculation first. Then demonstrate a asset_category filter and the acceptance check. Include the fixture, setup instructions, chosen tool versions, actual test output and one remaining limitation in the repository. If you show a screenshot, pair it with the input that produced it. Another learner should be able to repeat the same result from a clean checkout.

For a focused extension, add a second asset_category selection and compare the two groups using the same rule. Specify how missing groups appear and keep the original fixture as a regression case. Expand scope only after the current calculation, state handling and recovery path remain understandable.

Questions learners often ask

Which asset records belong in the result?

Select records whose status is exactly approved and that satisfy the chosen asset_category filter. Other states remain in the source data and can have separate summaries. Follow the domain rule above when a record changes state.

What should happen when no records match?

Return a zero total with a matching count of zero and a clear empty-result message. Keep the applied filter visible so the user can change it. Avoid using a loading indicator for a completed request that simply has no matching data.

How can I prove the size_kb result is correct?

Reconcile the first and third sample records, then repeat the calculation for Course Banner alone. Save both expected and actual outputs, and rerun the scenario-specific acceptance check after making a change.

Continue learning with Groot Academy

Use this exercise as a concrete discussion point when choosing a learning path. Explore the related Groot Academy course and ask about the current syllabus, learning mode and project practice. Course availability and batch details should be confirmed directly with the academy.

For implementation details, consult the official MongoDB documentation matching the tools you install. This project defines an original practice brief; it does not depend on a forecast about 2027 software releases.

Continue with Image Optimization Queue using MongoDB, or compare Digital Asset Catalogue using Flutter. These companion practice guides are part of the 2027 learning collection.