MWNF Inventory Documentation

MWNF Inventory replaces a fragmented legacy data landscape with one content-focused Inventory. The system stores museum content, organizes it through a rationalized model, and exposes it through an integrated Filament back-office and programmatic APIs.

The documentation starts with the business model and the import process because validation is the current priority. Technical references remain available, but they support the main explanation instead of driving it.

Start here

Audience	Start with	Purpose
Customers, content owners, and validators	Understanding the Inventory	Learn what the new model means and how legacy content lands in it.
Collaborators and developers	Collaborator Guide	Learn where the code lives and how the main systems fit together.
API consumers	Management API Reference	Inspect the authenticated management API and generated TypeScript client.
Data model reviewers	Database Models	Open generated model, field, and relationship reference pages.

What this system does

It stores reusable MWNF content only: objects, monuments, partners, collections, images, translations, glossary entries, timelines, links, tags, contributors, and related media.
It keeps application-specific configuration outside the Inventory model.
It uses /admin as the main back-office through Filament.
It keeps the management API as a maintained programmatic interface.
It prepares the ground for a dedicated read-only API optimized for lightweight public clients.

Validation focus

The project is at the import and validation stage. Use the documentation in this order:

Read Inventory Principles to understand what belongs in the Inventory.
Read Core Model to map legacy ideas to new concepts.
Read Legacy Import to understand the source-to-target flow.
Use Validation Guide when comparing legacy records with imported results.

Technical orientation

Collaborators should start with Codebase Map, then follow the page that matches the task:

Filament Back-Office for /admin UI work.
Importer Orientation for legacy data import work.
APIs and Documentation for API, OpenAPI, client, and Jekyll documentation work.
Development Workflow for setup, testing, and validation commands.

Reference material

Generated Database Models gives field-level model reference.
Management API Reference gives Swagger UI, OpenAPI, and TypeScript client links.
Deployment Guide keeps operational setup notes.
Technical Archive keeps older developer notes that still help maintainers, but the current project narrative lives in the new understanding/ and collaborators/ sections.

Last updated: May 28, 2026