King's College London · FACULTY OF ARTS & HUMANITIES

7AAVDH22 Chap.8 Preservation, Afterlife and Critical Reporting

- one subject, every graph, every model, every mark
6 Chapters5-page Bible
Our own words - no uploaded lecturer files
Updated for this semester
Chapter 8 of 8 · 7AAVDH22

Preservation, Afterlife and Critical Reporting

Preserve 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. Define what must survive: source evidence, a high-fidelity model, interactive behaviour, user contributions, design rationale or a combination.

Each target needs a different set of files and documentation.

Build a dependency package

Keep original captures, documented derivatives, master and delivery models, textures, storyboards and selected evaluation evidence. Record relationships between versions, formats, scale, coordinate assumptions and software or platform dependencies. Metadata supports identification, discovery and rights.

Paradata explains capture, reconstruction, optimisation and design choices. Neither layer should be assumed from filenames alone.

Plan stewardship and review

Open or widely supported formats can reduce risk but do not remove the need for monitoring, migration and validation. Store controlled copies, check integrity, name responsibility and identify events that trigger review.

Platform closure, format obsolescence, changed permission or loss of organisational ownership may each require a different response.

Technical availability must not be mistaken for ethical permission.

Use the four report areas as one argument

The source identifies presentation of the deliverable and interaction concept, rationale for the digital transformation, technical specifications with feasibility and execution, and critical reflection on concept, process and outcomes. Link them.

A capture limitation introduced under execution should return when the model is evaluated. An access risk in the rationale should be tested in the prototype and revisited in reflection.

Select consequential evidence

Critical reflection is strongest when it evaluates changed judgment.

Choose a moment, state the prior assumption, present evidence that challenged it, explain the revision and assess the remaining consequence. Routine software steps need only enough detail to make the decision understandable.

Screenshots should carry analytical work through captions and surrounding interpretation.

Synthesize a qualified recommendation

Conclude by naming the heritage problem, enabled encounter, strongest project evidence, important limitation, feasible stewardship and conditions for use. Avoid universal claims of accuracy, authenticity, accessibility or preservation.

The recommendation should be capable of changing when new evidence, audience needs, technical conditions or community authority changes.

In this chapter

What this chapter covers

  • 01

    Preservation Target

  • 02

    File Manifest

  • 03

    Metadata

  • 04

    Paradata

  • 05

    Critical Reflection

  • 06

    Qualified Recommendation

Worked example · free

Rescue a platform-dependent project

Q [10 marks]. AskSia-authored practice. A textured model exists only on a commercial viewer, while captures and process notes remain on personal devices. Build a preservation response. The marks shown are a study allocation, not an official university marking scheme.
Preservation is a dependency stack.Preservation is a dependency stack. Files become reusable evidence only when metadata identifies them, paradata explains transformations, and future users can judge rights and limitations. filesmaster and derivativechecksumsmetadataidentity and rightsrelationshipsparadatadecisions and limitsversionsreuseunderstandevaluate platform survival alone does not preserve meaning
Preservation is a dependency stack. Files become reusable evidence only when metadata identifies them, paradata explains transformations, and future users can judge rights and limitations.
  • 3Inventory files, versions and platform behaviour.
  • 4Add metadata, paradata, rights and relationships.
  • 3Specify controlled copies, responsibility and review.
Gather original captures, documented derivatives, master and delivery models, textures and a manifest. Record scale, versions, repairs, uncertainty, rights and platform dependencies. Store controlled copies with integrity checks and name a steward and review trigger. Document behaviour separately when it cannot be exported, without treating a recording as executable preservation.
Sia tip — Ask what would be impossible to understand or recreate if the hosting platform closed tomorrow, then add that evidence to the package.
Glossary

Key terms

Preservation Target
Preservation Target is the evidence, behaviour, context or experience selected to survive beyond initial delivery.
File Manifest
File Manifest lists assets, versions, relationships, formats and identifiers within a preservation package.
Interoperability
Interoperability supports use across systems through documented formats, structures, identifiers and relationships.
Technological Obsolescence
Technological Obsolescence occurs when formats, software, hardware or services can no longer be reliably used.
Critical Reflection
Critical Reflection evaluates how evidence changed a design judgment and what consequence remains.
FAQ

Preservation, Afterlife and Critical Reporting FAQ

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.

How should the four report areas connect?

The deliverable provides project evidence, the rationale explains purpose, feasibility and execution document consequential transformations, and reflection evaluates decisions and outcomes. Carry important issues across sections instead of describing each area as an isolated requirement.

What makes a strong final recommendation?

It joins heritage purpose, enabled encounter, project evidence, critical limitation, feasible stewardship and conditions for use. Calibrated verbs and visible uncertainty make the conclusion stronger because another evaluator can see what follows and what would change it.

Study strategy

Assessment move

Inventory your project as if the hosting platform vanished tomorrow. Separate originals, derivatives, masters, delivery files, documentation, rights and evaluation evidence. Draw the relationship between them and add a review trigger. For writing practice, choose one consequential decision and produce five sentences: assumption, evidence, revision, outcome and remaining limit.

Use those sentences to connect the report’s feasibility and reflection sections before drafting the final recommendation. Test the manifest by asking another person to identify the delivery model, its source assets and the rights condition without verbal help. Finish with a six-part recommendation covering purpose, encounter, evidence, limitation, stewardship and conditions for use.

Name the review event that would reopen the recommendation, such as a rights change, platform migration or community correction.

A+Everything unlocked
Unlocks this Bible + all 18 of your subjects at King's College London, plus 1,000+ more Bibles across the AskSia library.
Sia - your 7AAVDH22 tutor, unlimited, worked the way the exam marks it
The full 5-page Bible + practice bank with worked solutions
Chrome extension - sync your LMS so Sia knows your deadlines
Bilingual EN / Chinese on every Bible and every Sia answer
$0.99 Trial
30-day money-back · cancel in one tap · how it works
7AAVDH22 · Digital Interactions in Cultural Heritage - independent study guide on the AskSia Library. More King's College London subjects · Microeconomics across all universities