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:

1. Internal research and structuring
2. Review and validation
3. Public publication

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

Creating Structured Pages

Heritage Objects (HO:)

Steps:

1. Use the HeritageObject form
2. Enter required metadata
3. Save the page
4. Review stored data via queries if needed

Direct editing of HO pages without forms is discouraged.

Digital Assets (DA:)

Steps:

1. Upload file(s) (club members only)
2. Create a DA page using the DigitalAsset form
3. Link files to the DA
4. Link DA to one or more HO pages
5. Optionally define parent/child relationships between DAs

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

1. Upload file to File: namespace
2. Verify file name and format
3. Add file reference to a DA page
4. 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:

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

Internal DA pages remain private.

Schema Evolution Workflow

Changes to structure follow this order:

1. Update Cargo table
2. Save Cargo page to activate changes
3. Update Page Schema if needed
4. Regenerate forms if required
5. Test with sample data

Never change schema directly in the database.

Error Handling

If data does not appear as expected:

1. Check Cargo table definition
2. Check that the Cargo page was saved
3. Check form-to-field mapping
4. Check namespace and category constraints

Status

This workflow is considered stable but may evolve.