Design schema-driven field and form system for RIMS

[fusion94]

Description

RIMS should be reusable across multiple collection and inventory applications. To support this, item types, fields, validation, and form rendering should be driven by schema/configuration where practical rather than hardcoded per app.

This issue is for designing a flexible schema-driven system for:

• item type definitions
• field definitions
• validation rules
• generated or semi-generated forms
• consistent detail/list rendering patterns

Acceptance Criteria

• Define how item types are declared
• Define how custom fields are represented in schema/config
• Define validation strategy for schema-defined fields
• Define how forms are rendered from schema
• Define how detail/list views consume the same definitions where appropriate
• Produce a design note or implementation plan for the system