7AAVDM32 Chap.3 Digital Asset Lifecycle Models
Digital Asset Lifecycle Models
Actions and continuing controls
This chapter maps creation, appraisal, ingest, preservation, access and reuse while keeping description and planning visible across the whole lifecycle.
It compares models by function, granularity, direction and context instead of matching labels.
A model is an analytical lens
A lifecycle model selects and arranges activities so that responsibilities and transitions can be examined. It is not a claim that every asset follows one smooth path.
Some models emphasise sequential hand-offs, others recurring stewardship, and others the possibility of reuse, transformation or disposal. Compare them by asking which functions they make visible, what level of detail they use, how they represent iteration, and what organisational setting they assume.
Transitions carry evidence
The boundary between stages matters because evidence can be lost there.
At creation, provenance and technical context may be known informally. At ingest, that knowledge must become durable enough for later users. Appraisal records why an asset was selected, deferred or rejected. Preservation actions need a relationship between original and transformed objects. Access and reuse need current permissions and intelligible context.
A lifecycle analysis should therefore name both the action and the information that must cross each boundary.
Continuing activities cut across stages
Description, rights review, security, documentation and planning are not single boxes that can be completed forever.
Metadata may need correction after user feedback; permissions may expire or be renegotiated; risks may change as formats and platforms age; and organisational value may be reconsidered. Treating these as continuing controls reveals why a model with a simple visual sequence can still support repeated review.
Lifecycle debt accumulates
When an early action is skipped, later work becomes slower or less certain.
Missing provenance makes appraisal harder, an undocumented transformation weakens authenticity, and an unrecorded rights decision blocks reuse. Diagnose this lifecycle debt by starting with the visible failure and tracing backwards to the earliest transition at which necessary evidence was not captured or maintained.
The repair should address that originating weakness as well as the immediate symptom.
Adapt without erasing functions
A small organisation may combine roles and simplify terminology, but it still needs to decide what enters the managed environment, preserve essential properties, control access, document actions and review continuing value.
Adaptation should reduce unnecessary formality without deleting these functions. State who performs each action, what minimum record is required, and when a decision must be revisited. This makes the model proportionate rather than merely smaller.
Use comparison to justify design
When applying a model, explain why its structure fits the case.
A linear view may clarify a hand-off, while a cyclical view may better represent continuing stewardship and reuse. The closing exercise asks you to retain useful distinctions while modifying scale, vocabulary and responsibility for a particular organisation. The strongest answer acknowledges what the chosen model highlights, what it obscures, and which additional control compensates for that limitation.
What this chapter covers
- 01
Curation lifecycle
- 02
Full lifecycle actions
- 03
Appraise and select
- 04
Ingest validation
- 05
Preservation action
- 06
Access and reuse
Worked example · free
Choose a lifecycle model
- 2Identify the collection's significant risks.
- 3Compare model functions and coverage.
- 2Adapt roles without removing controls.
- 2State the remaining limitation.
Key terms
- Lifecycle Model
- A Lifecycle Model represents recurring actions and dependencies that support continuing management of digital material.
- Preservation Action
- Preservation Action protects long-term usability and the authoritative nature of managed material.
- Lifecycle Debt
- Lifecycle Debt is the later cost or uncertainty created by an earlier unmanaged decision.
Digital Asset Lifecycle Models FAQ
Why are some lifecycle actions continuous?
Description, representation information, preservation planning and community awareness influence many stages rather than one hand-off. Treating them as continuing controls explains how context and responsibility survive while assets move through sequential actions.
How should two lifecycle models be compared?
Examine what functions each includes, how detailed the stages are, whether revision or disposal is represented and which context the model assumes. Then choose or combine models for a defined decision and name the limitation that remains.
Can a small organisation use a complex lifecycle model?
Yes, if it maps required functions to feasible roles and services. One person may hold several roles, but appraisal, preservation, access and review decisions should remain distinguishable. Adaptation changes implementation; it should not silently erase a responsibility.
How do I compare two lifecycle models without matching labels?
Compare the functions each model makes visible, its level of detail, the direction and return paths it permits, and the organisational setting it assumes. Test both against the same difficult event, such as a rights hold or preservation transformation. Explain which model locates responsibility and evidence more clearly for that case, then identify what it obscures.
A justified choice can borrow an additional control from the alternative rather than claiming that one diagram is universally superior.
Assessment move
Rebuild the lifecycle from memory, then start with a later failure and trace backwards to the first missing record, control or responsibility. Add one return path and explain which continuing activity makes it necessary.