King's College London · FACULTY OF ARTS & HUMANITIES

7AAVDM32 Chap.4 Metadata Types and Dublin Core

- one subject, every graph, every model, every mark
6 Chapters4-page Bible
Our own words - no uploaded lecturer files
Updated for this semester
Chapter 4 of 9 · 7AAVDM32

Metadata Types and Dublin Core

Metadata with distinct functions

This chapter separates descriptive, structural and administrative metadata, then recombines them around user and management decisions. It uses Dublin Core as a practical element set while showing why consistent values and vocabulary authority matter as much as field labels.

Function comes before field

Descriptive metadata helps people identify and discover content.

Structural metadata records how components or versions relate. Administrative metadata supports management through technical, rights, provenance and preservation information. The categories can overlap in practice, so classify a field by the decision it supports in the case rather than memorising a label.

A date, for example, is only useful when its meaning is defined: creation, publication, capture, modification and rights expiry lead to different actions.

Dublin Core supplies a starting structure

Dublin Core offers broadly applicable elements such as title, creator, subject, description, publisher, contributor, date, type, format, identifier, source, language, relation, coverage and rights.

Applying the element set still requires local decisions about obligation, repeatability, value form and vocabulary. The label alone does not guarantee consistency.

A useful profile states what each selected element means for the collection, gives examples, and distinguishes unknown information from information that does not apply.

Values determine retrieval quality

Two records can use the same fields yet behave very differently in search. Free-text variants, unexplained abbreviations and mixed name orders fragment results, while uncontrolled dates impede sorting and review.

Controlled forms improve aggregation, but they also require authority, maintenance and a route for exceptions. Diagnose a retrieval problem at both levels: check whether the right concept has a field and whether the recorded values follow a usable rule.

Relationships carry structure

A compound work, its pages, a master file and its delivery rendition should not appear as unrelated objects.

Structural relationships let users navigate parts and wholes, distinguish versions, and trace derivatives to authoritative sources. Record the relationship type, not merely a shared keyword.

This makes it possible to explain what changed, select the appropriate object, and preserve context when files move between systems.

Records are situated claims

Metadata is produced by people and institutions for particular purposes. Description can preserve inherited bias, omit community knowledge or present uncertainty as fact.

Critical practice asks whose language has been adopted, which users benefit, who may be harmed or hidden, and how a disputed value can be challenged. An uncertainty note, source attribution and revision history can be more responsible than forcing a confident value into every field.

Critical record-making

You will audit uncertainty, omission and inherited categories instead of treating structure as neutrality.

The final repair exercise tests whether a record supports discovery, interpretation, permitted use and continuing stewardship. A complete repair names the failed user task, the field or relationship involved, the proposed value rule, its authority, and the person responsible for review. It also checks that technical tidiness has not erased meaningful ambiguity.

In this chapter

What this chapter covers

  • 01

    Descriptive metadata

  • 02

    Structural metadata

  • 03

    Administrative metadata

  • 04

    Dublin Core

  • 05

    Controlled values

  • 06

    Metadata quality

Worked example · free

Describe an exhibition photograph

Q [8 marks]. Create a compact Dublin Core record without inventing personal names, dates or rights. Marks shown here are AskSia guidance, not an official university mark allocation.
Metadata roles overlap but are not interchangeable.Metadata roles overlap but are not interchangeable. Description supports discovery, structure connects parts, and administration governs continuing management. Descriptiveidentifydiscoverinterpret Structuralordernavigaterelate parts Administrativerightstechnical controlpreservation Together they make an object findable, intelligible and governable
Metadata roles overlap but are not interchangeable. Description supports discovery, structure connects parts, and administration governs continuing management.
  • 2Identify verified descriptive facts.
  • 3Choose appropriate elements and value forms.
  • 3Record rights and uncertainty states.
Use a verified descriptive title, Creator and Date only where supported, Format for the image type, controlled Subject terms, Coverage for place, Rights for permission and a stable Identifier. Mark unresolved values rather than guessing, then review the record for internal coherence.
Sia tip — Classify a field by the decision its value supports.
Glossary

Key terms

Descriptive Metadata
Descriptive Metadata identifies and explains a resource for discovery and interpretation.
Structural Metadata
Structural Metadata records how parts sequence, combine or relate within an object.
Administrative Metadata
Administrative Metadata supports rights, technical control, access and preservation.
FAQ

Metadata Types and Dublin Core FAQ

Why do metadata types overlap?

A value can serve different functions depending on its meaning and use. A date may describe creation, trigger a rights review or document migration. Classify the field by the decision it supports and preserve its definition so people do not mix unrelated facts.

Does Dublin Core guarantee good metadata?

Dublin Core supplies shared element names, but cataloguers still choose values, sources, granularity and controlled forms. A technically valid record can be vague, inconsistent or misleading. Test the completed set against real discovery, interpretation and management tasks.

How should unknown metadata be handled?

Distinguish unknown, not collected, intentionally withheld and not applicable where the system allows. Preserve the evidence and assign a review route. Filling a gap with a plausible value creates false certainty and can mislead search, rights and interpretation.

What makes a compact metadata profile defensible?

Start with the discovery, interpretation, rights or preservation decisions the collection must support. Select fields for those functions, define what each field means locally, set value forms and authorities, and show how uncertainty is recorded. Test the profile on compound objects, disputed descriptions and ordinary records.

A defensible profile is not the one with the most elements; it is the one another cataloguer can apply consistently and a user can connect to a meaningful next action.

Study strategy

Assessment move

Take one object and sort its fields by descriptive, structural and administrative function. Then remove every value you cannot verify and design a clear uncertainty state. Test the revised record against one realistic search and one rights decision.

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 7AAVDM32 tutor, unlimited, worked the way the exam marks it
The full 4-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
7AAVDM32 · Introduction to Digital Asset and Media Management - independent study guide on the AskSia Library. More King's College London subjects · Microeconomics across all universities