Design the neutral RIMS core data model

[fusion94]

Description

RIMS needs a domain-neutral data model that supports multiple inventory and collection systems without leaking app-specific concepts into the core.

The model should support shared structural concepts such as:

• items
• categories or types
• custom fields
• locations
• status/lifecycle
• events/history
• attachments
• auditability

This issue is for defining that model clearly before implementation or migration work proceeds.

Acceptance Criteria

• Define the core entities needed by RIMS
• Document relationships between items, categories, custom fields, events, and attachments
• Define lifecycle/status concepts in a domain-neutral way
• Define how locations/storage should work generically
• Document where audit trail data belongs
• Produce a schema or architecture note suitable for implementation planning