Original practice scenario: A hypothetical research platform renames sample categories and splits one category into two. Existing studies still reference the old category. Design a compatible vocabulary model.
Read model answer +
Use stable concept identifiers and versioned meaning rather than treating display labels as keys. A category split changes classification semantics and cannot be represented faithfully by a simple rename.
Work through it
Store concept identity, labels, validity and relationships such as replacement or narrower category, preserving the vocabulary version used by each source record.
Define whether historical records can be reclassified from available evidence; retain unknown or ambiguous assignments when the old category lacks sufficient detail.
Support current and historical views through explicit mappings, testing merges, splits, retired concepts and localized labels with clear provenance.
Tradeoffs to discuss
A current simplified vocabulary aids discovery but may lose historical distinctions; parallel versioned views improve fidelity while increasing mapping maintenance.
Common pitfalls
Do not assign every old record to one new category merely to satisfy a required field.
Two labels that look similar may encode different experimental meanings and should not automatically share an identifier.
Original practice scenario: A hypothetical pharmaceutical supply dashboard tracks lots, transfers, expiration dates and quarantine decisions. Explain how to calculate an as-of inventory view without making a product-use decision.
Read model answer +
Calculate stock from identified movements and report disposition separately. An expiration comparison alone does not establish whether a lot is available, released, quarantined or otherwise restricted.
Work through it
Aggregate receipts, transfers, consumption and authorized adjustments at lot-location grain, using the movements known by the reporting cutoff.
Join the effective lot expiry and reviewed disposition state without multiplying movements, preserving missing or conflicting attributes as exceptions.
Show quantities by declared expiry bands and disposition categories, reconciling the sum with physical stock controls and recording the snapshot version.
Tradeoffs to discuss
A current-state dashboard is convenient for operations, while historical replay needs effective dates and knowledge-time records for corrections.
Common pitfalls
Do not count a transfer simultaneously as new global stock and a destination receipt.
The technical report must not override authorized release rules or infer permission to use a product from date arithmetic alone.
