7AAVDH22 Digital Interactions in Cultural Heritage
7AAVDH22 Overview
- Semester 1, 2026/27
- Postgraduate module
- 4,000-word report
- Single assessment
What this module connects
Digital Interactions in Cultural Heritage joins critical heritage thinking with practice-based digital design.
- Start with heritage value Technology serves a named heritage problem, audience and evidence base.
- Document transformations Capture, modelling and optimisation choices become paradata and report evidence.
- Test situated access Evaluate the essential task across barriers, routes and represented voices.
- Plan the afterlife Files require metadata, rights, context and stewardship to remain evaluable.
How 7AAVDH22 is assessed
| Component | Weight | Format |
|---|---|---|
| 4,000-word critical design report | 100% | Low-spec 3D heritage deliverable with critical evaluation |
The captured KCL syllabus and assessment slides publish one 4,000-word critical design report worth 100%, due 12 January 2027 at 14:00.
Assessment structure
The published component carries the full module weight.
Current 7AAVDH22 dates
| Date | Item | Control |
|---|---|---|
| 15 December 2026 | Submission activity opens | Published in the captured KEATS syllabus. |
| 12 January 2027, 14:00 | Critical design report due | Published in the captured KEATS syllabus. |
Dates are as published in the captured Semester 1, 2026/27 KEATS syllabus. Confirm exact submission instructions in KEATS.
What 7AAVDH22 covers
Eight source-led chapters connect heritage values, 3D capture, interaction, access, preservation and critical reporting.
Heritage Values and the Phygital Continuum
Classify physical and digital dependencies without reducing heritage to a mediumBegin with the heritage relation
Heritage is not a container into which old objects are placed. The module asks how heritage is constructed, valued and authorised, so analysis begins with people, practices and evidence.
- Heritage Value
- Authorised Heritage
- Phygital Continuum
- Digital Dependency
- Born-Digital Heritage
- Qualified Representation
Critical Design, Audiences and Purpose
Turn a heritage problem into a meaningful, testable audience interactionWrite the problem before the technology
Critical design begins with a gap, tension or opportunity grounded in heritage evidence.
- Heritage Problem
- Situated Audience
- User Action
- Interaction Response
- Risk Review
- Evaluation Claim
Capture Planning and Paradata
Plan coverage, lighting and scale while documenting consequential capture decisionsTranslate the heritage claim into a capture goal
Photogrammetry begins before the camera moves. Identify the feature, scale or context that the model must support.
- Capture Goal
- Image Overlap
- Surface Constraint
- Scale Reference
- Paradata
- Coverage Audit
From Photographs to a Defensible 3D Model
Trace photographs through alignment, point clouds, meshes, textures and optimisationFollow the reconstruction pipeline
The modelling seminar introduces alignment, point clouds, meshes, textures and optimisation. Each stage changes the representation. Alignment estimates camera relationships from shared features.
- Camera Alignment
- Point Cloud
- Mesh Topology
- Texture Projection
- Model Optimisation
- Fitness For Purpose
Embodiment, Affordances and Authenticity
Evaluate situated user actions and qualify claims of authentic digital experienceAnalyse the whole encounter
The interaction lecture treats digital heritage experience as socio-culturally constructed. Heritage evidence, interface controls and embodied context work together.
- Embodied Context
- Affordance
- Interface Mediation
- Visual Realism
- Authenticity Relation
- Situated Evaluation
Access, Exclusion and Represented Voices
Test barriers, participation and authority behind claims of wider digital accessChallenge automatic democratisation
The access lecture asks who gains access, who remains excluded and whose interpretation is represented.
- Access Claim
- Essential Task
- Barrier Trace
- Alternative Route
- Represented Voice
- Governance
Accessible Interaction Prototypes
Storyboard physical-digital touchpoints and revise the essential interpretative taskStoryboard the encounter
The accessible-design seminar asks teams to define audiences, interaction sequences, interfaces and physical-digital touchpoints around their 3D content.
- Storyboard
- Interaction Sequence
- Physical Touchpoint
- Paper Prototype
- Task Observation
- Iteration Record
Preservation, Afterlife and Critical Reporting
Preserve files and context, then synthesize a qualified design recommendationPreserve more than a live link
The preservation lecture challenges the assumption that digitisation equals preservation. A hosted experience may work today while its captures, scale, rights and processing history remain scattered.
- Preservation Target
- File Manifest
- Metadata
- Paradata
- Critical Reflection
- Qualified Recommendation
The source moves from questions about how heritage is constructed, valued and authorised into photogrammetry, 3D reconstruction, embodied interaction, access, preservation and public presentation. Technology is never the whole answer.
Each intervention must be related to an object, place, practice or record, a situated audience and a cultural or ethical claim.
How the guide follows the teaching sequence
The opening chapters distinguish heritage value from medium and turn an audience problem into a testable interaction. Capture planning then treats lighting, coverage, scale and difficult surfaces as evidence decisions.
Reconstruction follows photographs through alignment, point clouds, meshes, textures and optimisation, keeping paradata beside every consequential transformation. Later chapters test embodiment, affordances, authenticity, access, represented voices and the physical-digital touchpoints of a prototype.
What the assessment requires
The captured material publishes one 4,000-word critical design report worth 100%.
It combines a low-spec 3D heritage deliverable with critical evaluation. The report presents the deliverable and interaction concept, explains the rationale for digital transformation, addresses technical specifications, feasibility and execution, and critically reflects on the concept, process and outcomes.
The source does not provide a percentage split between those areas or a detailed marking rubric.
What strong project evidence looks like
Useful evidence includes a clear heritage claim, capture and model diagnostics, dated design versions, user-task observations, documented access routes, source attribution, rights conditions and a preservation package. A polished screen or model is not enough.
The report should explain why a decision was made, what evidence challenged it, what changed and which limitation remains. Operational submission and academic-integrity requirements should be checked in the live KEATS activity.
Worked example · free
Reframe a technology-led heritage proposal
- 2Name the heritage problem and supporting evidence.
- 3Define audience, action and interface response.
- 3Add a risk test and qualified evaluation claim.
Key terms
- Cultural Heritage
- Cultural Heritage is a valued object, place, practice or record whose significance is constructed and sustained through social relations.
- Phygital Heritage
- Phygital Heritage describes an experience in which physical and digital elements jointly shape interpretation.
- Photogrammetry
- Photogrammetry reconstructs spatial form by relating overlapping photographs taken from different viewpoints.
- Paradata
- Paradata records consequential production decisions, transformations and uncertainties that ordinary file metadata does not explain.
- Point Cloud
- Point Cloud is a set of estimated spatial samples produced during 3D reconstruction before a continuous surface is built.
- Mesh
- Mesh is the connected geometric surface constructed from spatial evidence and processing decisions.
- Texture
- Texture is image-derived appearance projected onto model geometry and may retain lighting or capture artefacts.
- Affordance
- Affordance is an actionable possibility that emerges between a user, interface and context.
- Embodiment
- Embodiment describes how bodily position, senses, movement and environment shape a digital heritage encounter.
- Accessibility
- Accessibility is the situated ability of named users to reach, perceive, understand and act through an experience.
- Interoperability
- Interoperability is the capacity for files and information to remain usable across systems through documented structures and relationships.
- Digital Afterlife
- Digital Afterlife concerns how heritage files, contexts, rights and dependencies persist after initial creation and dissemination.
7AAVDH22 FAQ
What is the assessment structure?
The captured module material publishes one 4,000-word critical design report worth 100%. It combines a low-spec 3D heritage deliverable with critical evaluation across rationale, technical feasibility and execution, and reflection on concept, process and outcomes. Check the live KEATS activity for current submission instructions.
Does the module require coding?
The module description says no coding is involved. The practical work uses 3D capture, modelling and interaction design while emphasising critical evaluation of cultural, technical and ethical choices. Students still need to understand the transformations introduced by tools rather than treating software output as neutral.
How should a heritage object be classified?
Separate the material object, living practice, record and digital representation, then identify the values and communities connecting them. A continuum label is useful only when it clarifies physical, platform or social dependencies and changes a later capture, interaction or preservation decision.
What makes a 3D model defensible?
A defensible model traces visible form back to overlapping photographs, scale and documented reconstruction choices. It distinguishes observed surfaces from interpolated or edited geometry, records uncertain regions in paradata and limits claims to the features and uses actually checked.
How is accessibility evaluated?
Name the intended audience and essential interpretative task, then test device, sensory, motor, language, knowledge and contextual barriers along the route. Report which alternatives preserve the task, which users were assessed and which exclusions or governance questions remain.
What should a preservation package contain?
Retain original captures, documented derivatives, master and delivery models, textures, metadata, paradata, rights conditions, version relationships and platform dependencies. Controlled copies, integrity checks, stewardship responsibility and a review trigger help future users understand and evaluate the project.
How should critical reflection be written?
Select consequential decisions and state the prior assumption, evidence that challenged it, revision made and remaining consequence. Connect technical transformations to embodied, cultural, aesthetic and ethical implications, then make a qualified recommendation rather than listing production difficulties.
Questions students ask in each 7AAVDH22 chapter
- Is digital heritage less authentic than material heritage?
- Material and digital forms create different dependencies rather than a simple authenticity ranking. Evaluate which evidence, social relations and technical conditions each form retains, transforms or loses. A transparent digitised model may support stronger interpretation than a realistic but undocumented reconstruction. Chapter 01 · Heritage Values and the Phygital Continuum
- What makes an interaction meaningful?
- A meaningful interaction changes how a named audience encounters or interprets heritage evidence. It specifies the user action, interface response and cultural purpose, then tests whether the result supports understanding, participation or another stated outcome rather than measuring novelty alone. Chapter 02 · Critical Design, Audiences and Purpose
- How many photographs are enough for capture?
- There is no useful universal count. The image set needs connected overlap, adequate viewpoints for important surfaces, stable appearance and the scale required by the intended use. Audit coverage and uncertainty rather than treating file quantity as evidence of quality. Chapter 03 · Capture Planning and Paradata
- Why can a realistic model still be wrong?
- Texture can conceal distorted or generated geometry, and visual polish does not show whether views aligned correctly. Compare silhouette, scale, diagnostic features and uncertain regions against source photographs and paradata before making fidelity claims. Chapter 04 · From Photographs to a Defensible 3D Model
- What is an affordance in digital heritage?
- It is the action a particular user can perform through an interface in context, together with the possibility that action opens. Describe the control, bodily and technical demands, system response and interpretative consequence rather than treating affordance as a feature label. Chapter 05 · Embodiment, Affordances and Authenticity
- Does putting heritage online democratise access?
- Online publication may expand remote reach, but it also introduces device, network, sensory, motor, language and platform conditions. A defensible claim names the audience and task, tests routes, reports exclusions and examines who controls representation. Chapter 06 · Access, Exclusion and Represented Voices
- What should a heritage storyboard include?
- Show entry context, heritage evidence, user action, system response, physical-digital transitions, alternative routes and the next interpretative possibility. A storyboard should expose assumptions and decisions rather than imitate the final visual style. Chapter 07 · Accessible Interaction Prototypes
- Why is digitisation not the same as preservation?
- A digital file can survive while scale, provenance, software, rights and production decisions disappear. Preservation keeps enough evidence and context for future users to understand, evaluate and, where permitted, reuse the material under changing technical conditions. Chapter 08 · Preservation, Afterlife and Critical Reporting
How to prepare for the assessments
Work in project order but revise whenever evidence changes the heritage claim. First write a one-sentence relation between heritage value, audience and the limited digital role. Build a decision ledger for capture, reconstruction and interaction, attaching dated evidence to each consequential change. After every chapter, complete one practice task without notes and identify the first unsupported assumption.
Test the essential user task through at least one alternative route, keeping accessibility and representation connected. During report drafting, trace one limitation from its origin through the response and final evaluation. Rebuild the four report areas as a single argument: deliverable, rationale, feasibility and execution, then critical reflection.
Before submission, read topic sentences and captions alone, verify that each broad adjective has evidence, check rights and personal information, preserve the project package independently, and confirm current operational requirements in KEATS.