Jump to content

ICT:HO-Procedure

From Costa Sano MediaWiki
Revision as of 17:02, 22 January 2026 by Mngr (talk | contribs) (Created page with "= Procedure – Creating a HeritageObject (HO) = This page explains how to create a HeritageObject. A HeritageObject is the central historical or conceptual entity under study. Examples: * building * document * person-related artifact * equipment * archive register * architectural element HeritageObjects anchor all research meaning. == When to create a HeritageObject == Create a HeritageObject whenever: * something is studied or described in the research * mult...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Procedure – Creating a HeritageObject (HO)

This page explains how to create a HeritageObject.

A HeritageObject is the central historical or conceptual entity under study.

Examples:

  • building
  • document
  • person-related artifact
  • equipment
  • archive register
  • architectural element

HeritageObjects anchor all research meaning.


When to create a HeritageObject

Create a HeritageObject whenever:

  • something is studied or described in the research
  • multiple files refer to the same thing
  • you need a stable conceptual reference

Rule of thumb:

If you can write a paragraph about it, it is probably a HeritageObject.


Step-by-step workflow

Step 1 – Create the page

Open:

Special:FormEdit/HeritageObject


Step 2 – Fill basic information

Complete:

  • Title
  • Type
  • Description
  • Dates (if known)


Step 3 – Structure (optional)

If this object is part of a larger object:

Use "Parent object".

Examples:

  • Ward → parent: Hospital
  • Door → parent: Facade
  • Register page → parent: Register

This creates conceptual hierarchy.


Under "Digital assets":

Select all DigitalAssets that represent this object.

Examples:

  • scan
  • photo
  • OCR
  • drawing

This connects interpretation to meaning.


Step 5 – Add people and organisations

Add:

  • Persons with roles (creator, restorer, author, etc.)
  • Organisations with roles (owner, operator, etc.)

Roles describe involvement.

They belong to the relationship, not the person itself.


Step 6 – Add holders (if applicable)

Add current holders:

  • responsible person
  • managing organisation

Holders describe present responsibility only, not historical ownership.


Assign the object to one or more ResearchChapters.

This determines where the object is discussed in the narrative structure.


Step 8 – Add keywords

Add tags to help discovery.


Step 9 – Save

Done.


Good practices

✓ one clear concept per HO page ✓ write meaningful descriptions ✓ use hierarchy for structure ✓ link all relevant DigitalAssets ✓ use roles consistently

Avoid:

✗ mixing multiple unrelated concepts in one HO ✗ storing files directly on the HO page ✗ creating HOs only for storage purposes