View source for ICT:Workflow

= Operational Workflow =

This page describes how data, pages, and media are created, edited, and published.

It focuses on practical day-to-day workflows.

== General Workflow Principle ==

Work proceeds in phases:

# Internal research and structuring
# Review and validation
# Public publication

Internal work may be complex and incomplete.
Public output must be stable and curated.

== Creating Structured Pages ==

=== Heritage Objects (Heritage:) ===

Steps:

# Use the HeritageObject form
# Enter required metadata
# Select elements for automatic numbering
# Save the page
# Review stored data via the provided dashboard

Editing of Heritage: pages goes through the dashboard. Heritage: pages are for internal viewing.

=== Digital Assets (Asset:) ===

Steps:

# Create an Asset: page using the Asset:Dashboard
# Select elements for automatic numbering.
# Filenames ares the same as the automatic name for Assets.
# Link files to the DigitalAsset
# Link the Asset to one or more Heritage: pages
# Optionally define parent/child relationships between Assets

DA pages are internal and not intended for public viewing.

== Managing Relationships ==

Many-to-many relationships are handled using:

* Cargo subtables
* Repeatable form sections

Examples:
* Object–Person relationships
* Object–Set memberships

Relationships are always edited in the context of a parent page.

== File Upload Workflow ==

# Files are uploaded via DigitalAssets pages.
# File name and format
# Add file reference to a DA page
# Do not embed internal files on public pages

File uploads are restricted to club members.

== Public Publication Workflow ==

Publication is a deliberate act.

Typical steps:

# Identify content ready for publication
# Create or select a public file derivative
# Embed the public file on a page in the Main namespace
# Verify that no internal files are referenced

Internal DA pages remain private.

== Schema Evolution Workflow ==

Changes to structure follow this order:

# Update Cargo table
# Save Cargo page to activate changes
# Update Page Schema if needed
# Regenerate forms if required
# Test with sample data

Never change schema directly in the database.

== Error Handling ==

If data does not appear as expected:

# Check Cargo table definition
# Check that the Cargo page was saved
# Check form-to-field mapping
# Check namespace and category constraints

== Status ==

This workflow is considered stable but may evolve.