Make preservation of website material easier to navigate.
Explore preservation of website material, with practical workflows, a working example and checks for common mistakes.
Explore the guide ↗Web Archive Practice is a focused resource for content owners and archivists, exploring preservation of website material through the work people actually need to perform. For this topic, the workflow is to identify material worth retaining, record context and versions, and choose a retrieval approach. This guide uses a website preservation inventory to hold the decisions together and examines capture scope, version dates and retrieval context as distinct quality concerns.
The example involves an organisation preserving an old service website before replacement; it is an illustrative exercise for this subject, rather than a reported client result. An archive needs context for retrieval. Record what was captured, when and why, and distinguish preserved historical material from current guidance so a future reader does not mistake an old page for the live service.
Ideas into action
WEB / 10 SECTIONSStart by describing the task that makes preservation of website material relevant now. Use the situation of an organisation preserving an old service website before replacement to identify the practical question before choosing a method. A concern involving capture scope may require different evidence from a concern involving version dates.
Keep those questions visible in a website preservation inventory, alongside the intended outcome. The scope of preservation of website material becomes easier to discuss when an agreed requirement is clearly distinguished from an idea that still needs investigation. Before proceeding with preservation of website material, decide whether the current state of retrieval context creates a dependency that needs another person's input.
A website preservation inventory
Use a website preservation inventory as a shared reference for this piece of preservation of website material. The record is especially useful when content owners and archivists need to explain why a particular route was chosen. Connect the entry about capture scope to the relevant evidence for preservation of website material, rather than copying information without its source context.
Review a website preservation inventory after a meaningful change; an abandoned reference can mislead the next person working on preservation of website material.
Identify material worth retaining
The first working stage is to identify material worth retaining. In the example involving an organisation preserving an old service website before replacement, identify which input is needed before this action can produce a dependable result. Consider how questions about capture scope affect the starting conditions for the action to identify material worth retaining, including information that has not been confirmed.
Record the outcome in a website preservation inventory and explain any limitation before asking somebody to record context and versions. This creates a traceable starting point for preservation of website material, making an incomplete input easier to recognise before it influences the rest of the work.
Record context and versions
Continue by deciding how to record context and versions under the agreed conditions. The handoff from the first stage of preservation of website material should contain the information this action actually requires. Before you record context and versions, inspect version dates and identify any assumption that has become doubtful.
If the situation involving an organisation preserving an old service website before replacement reveals a different requirement, update a website preservation inventory before expanding the work. A visible change decision keeps preservation of website material coherent and helps the next participant understand whether the original scope still applies.
Choose a retrieval approach
05 / 10The third stage is to choose a retrieval approach, bringing the current piece of preservation of website material to an understandable state. Check retrieval context against the agreed purpose of preservation of website material, not merely against a list of completed activities. Use a website preservation inventory to identify follow-up responsibilities and relevant limits.
In the example of an organisation preserving an old service website before replacement, ask what the receiving person would need before relying on the output. Closing this stage of preservation of website material clearly prevents an unfinished dependency from being mistaken for an accepted result.
Avoid saving files without knowing what they represent
A specific failure pattern in preservation of website material is saving files without knowing what they represent. It can create a gap between the appearance of progress and the actual outcome needed by content owners and archivists. Check whether capture scope was understood before the action began and whether version dates was examined by somebody with the relevant context.
Capture the correction in a website preservation inventory, including its effect on retrieval context. The aim is to reduce the opportunity for saving files without knowing what they represent to recur, while keeping the process proportionate to the work.
Consider an organisation preserving an old service website before replacement as a small rehearsal of preservation of website material. Write down the request and expected result, then identify who performs the action to identify material worth retaining. Before moving to the instruction to record context and versions, ask which information the next participant needs.
Use a website preservation inventory to preserve any question the example exposes, especially where capture scope is uncertain. Then decide how to choose a retrieval approach without hiding a concern about retrieval context.
Check version dates
The review criteria for this guide are capture scope, version dates and retrieval context. Examine each criterion separately in the context of preservation of website material, because a positive finding in one area does not settle the other questions. For content owners and archivists, a useful review records what was examined and how the finding affects the next action.
Connect the evidence to a website preservation inventory, including any limitation in the material available. In the situation involving an organisation preserving an old service website before replacement, identify which finding would prevent a responsible handover. This approach makes the review of preservation of website material explainable, rather than treating an unexplained approval label as evidence that the task is ready.
Keep the guidance useful after the first pass
Maintenance of preservation of website material should respond to changes in the task, its inputs and its responsible people. Assign an owner to a website preservation inventory and explain which events should trigger another review. A changed assumption about capture scope may affect the earlier decision to identify material worth retaining; a concern about retrieval context may require a new closing check.
Remove obsolete directions from a website preservation inventory deliberately so that earlier versions do not compete with approved guidance. When version dates changes, explain whether the instruction to record context and versions needs different inputs or a revised decision.
Choose a practical next step
Begin with one bounded task involving preservation of website material rather than a complete redesign of the surrounding operation. Prepare a website preservation inventory, work through the three actions and inspect the result using the criteria for capture scope, version dates and retrieval context. Ask someone from the intended audience of content owners and archivists to identify a point that still needs clarification.
Compare that observation with the example of an organisation preserving an old service website before replacement, then choose a specific change worth testing.