Media

Keep support material attached

flowchart LR
    Scattered[Scattered files and assets] --> Media[Media record]
    Media --> Context[Governed context]
    Media --> Connections[Entity links]
    Media --> Evidence[Evidence support]

Teams rarely fail because they lack files. They fail because useful files are disconnected from the records they actually explain, leaving evidence orphaned and relationship meaning invisible.

A media record gives the team one governed place to answer questions such as:

• what is this file and what category does it belong to
• what is the human-curated summary or description
• what content was extracted or derived from the original upload
• which trials, contacts, organizations, sites, interventions, or other entities connect to this asset

That matters because downstream decisions depend on whether supporting material is linked to the right records, not just whether it was uploaded somewhere.

Separate the file from the meaning

flowchart LR
    Media[Media] --> Trials[Trials]
    Media --> Contacts[Contacts]
    Media --> Organizations[Organizations]
    Media --> Sites[Sites]
    Media --> Interventions[Interventions]
    Media --> Personas[Personas]

TrialStack treats media as supporting context, not as a substitute for the governed record it belongs to. The page keeps both file information and relationship meaning visible so reviewers can assess what the asset is and where it matters.

Put media to work

flowchart LR
    Media[Media record] --> Identify[Describe the asset]
    Media --> Summarize[Curate the summary]
    Media --> Connect[Link to records]
    Media --> Review[Review connections]

The page is especially useful when a team needs to:

• describe the asset with name, category, and tags
• curate the human-facing description or summary
• review extracted or analysis-derived content
• check which records depend on this asset before making changes

On the page

The media page is intentionally compact — two sections for the asset itself plus relationship tabs showing where it matters.

Surface	Purpose	What users do there
Summary	Maintain asset identity and content	Capture name, category, description, tags
Relationship tabs	Show where the asset matters	Review linked trials, contacts, organizations, sites, interventions, personas

classDiagram
    class MediaPage {
        +Summary
        +RelationshipTabs
    }

    class Summary {
        +Information
        +Content
    }

    class RelationshipTabs {
        +Trials
        +Contacts
        +Organizations
        +Sites
        +Interventions
        +Personas
    }

    MediaPage *-- Summary
    MediaPage *-- RelationshipTabs

What to capture

mindmap
  root((Strong media records))
    Clear asset identity
    Meaningful category and tags
    Curated description
    Extracted or derived content
    Visible entity connections

A strong media record is not just a file upload. It makes clear what the asset is, what it means, and where it connects.

Good media records usually do three things well:

• they describe the asset clearly with name, category, and tags
• they provide a curated summary that explains the file’s relevance
• they maintain real connections to the entities that depend on the asset

That is why only Name is required. The point is to capture the context that makes the asset useful for downstream decisions.

Information

mindmap
  root((Information))
    Name
    Original filename
    Media type
    Category
    MIME type
    Size

This section describes the asset itself. Some fields are system-detected from the upload and remain read-only.

Label	Description	Type
Name	Display name for the media asset	Text
Original Filename	Filename as uploaded — system-detected	Read-only text
Media Type	Detected media type such as document, image, audio, video	Read-only select
Media Category	User-assigned category for organizational grouping	Select
MIME Type	Detected MIME type of the file	Read-only text
Size	File size — system-detected	Read-only text

Content

mindmap
  root((Content))
    Description
    Tags

This section holds the human-maintained summary and tagging context.

Label	Description	Type
Description	Curated summary or description of the asset and its relevance	Rich text
Tags	Free-form tags for categorization and search	Tags