Asset Chain Model and Selection Strategy

Purpose

This document defines the **Asset Chain model** used in this system and explains:

how Assets are versioned
how “top assets” are defined
how Assets are selected easily by users
how the full Asset chain can be displayed consistently

The model is designed to:

remain simple for historian users
avoid complex custom code
scale to large collections (1000+ Assets)
keep editorial intent explicit and stable over time

---

Core Principles

One Asset represents **one file**
Assets may have multiple **versions**
Versions are grouped into **Asset chains**
Other entities (Object, Person, Place, etc.) link to **one Asset only**
That Asset acts as the **entry point to the full chain**

---

Asset Chain Definition

Top Asset (Chain Root)

The **first Asset created** for a subject
Has **no parent Asset**
Is the **top asset permanently**
Represents:

 * recognition thumbnail
 * subject identification
 * entry point for the chain

The definition of “top asset” is **structural**, not qualitative:

it is NOT “best quality”
it is NOT “highest resolution”
it does NOT change later

---

Child Assets (Versions)

Represent alternative versions of the same Asset

 (e.g. better scan, restoration, derivative)

Always have a **parent Asset**
The parent **must be the top asset**
Children of children are **not allowed**

This creates a constrained structure:

Top asset (no parent)
├── Version A
├── Version B
├── Version C

No deep or random trees are permitted for Assets.

---

Editorial Workflow

Creating an Asset Chain

1. User creates the first Asset

  * Parent field left empty
  * Asset becomes the **top asset**

2. User creates a new version

  * Parent selected = top asset

3. Repeat for additional versions

At no point does the user need to redefine or move the top asset.

---

Linking Assets to Other Entities

Object / Person / Place entities link to:

 * **exactly one Asset**
 * always a **top asset**

This link never changes when new versions are added

Benefits:

stable references
no cascading updates
no hidden automation

---

Asset Selection (Entity Browser)

User Interface Principle

Users should:

see **only top assets**
search using **one simple search box**
never need to understand Asset chains

---

Entity Browser View Rules

The Asset selection View applies:

1. **One exposed filter (visible)**

  * Combined fields filter
  * Searches across:
    * title
    * identifiers
    * keywords
    * other metadata fields

2. **Additional filters (not visible)**

  * Asset has no parent (top assets only)
  * Content type = Asset

Important:

Only the first exposed filter is shown in the modal
All other filters are still applied silently

Result:

clean UI
strong constraints
no risk of selecting a child asset

---

Presenting the Asset Chain

Asset Chain View

A dedicated View is used to show the full chain.

Definition:

Contextual argument = top asset ID
Filters:

 * Asset ID = argument
 * OR parent Asset = argument

Sorting:

 * creation date
 * version label
 * or other editorial order