University College London · FACULTY OF INFORMATION TECHNOLOGY

INST0089 Information Organisation and Description

- one subject, every graph, every model, every mark
6 Chapters29-page Bible
Our own words - no uploaded lecturer files
Updated for this semester
The Complete Study & Assessment Guide · Term 1 and Term 2

INST0089 Overview

Information Organisation and Description
— define the resource, model its meaning and defend every encoding choice
  • University College London
  • Academic Year 2026/27
  • Level 2
  • Coursework assessed

INST0089 Information Organisation and Description develops the judgement needed to describe resources for people and systems. The module begins by asking what the resource is, which descriptive boundary applies and what an audience needs to do. Identity, content and context are treated as complementary layers.

  • Boundary first Define the resource and its level before selecting metadata fields.
  • Meaning before format Keep the metadata model stable while comparing technical representations.
  • Validation layers Check syntax, schema, semantics and the actual user scenario separately.
  • Defended choices Link every design decision to evidence, consequence and limitation.
Why read this guide

What you get in the full INST0089 Study & Assessment Guide

  1. 6 chapters, 29 pages — every assessed topic, week by week
  2. 15 original practice questions, each with a model answer
  3. 6 worked examples, solved the way INST0089 marks
  4. 13 computed figures, redrawn from the course’s own numbers
  5. Before-you-submit checklist for the Part 2 (60%) — what markers reward, what costs marks

Free on this page: assessment table, chapter map, one worked example, key terms, FAQ. The rest is in the full study & assessment guide.

INST0089 · University College London
An independent, AskSia-authored study guide. AskSia is not affiliated with, endorsed by, or sponsored by University College London; the course code and name are used for identification only.
Assessment

How INST0089 is assessed

ComponentWeightFormat
Part 140%Summative Project/Portfolio using a resource collection and metadata schema, plus a 1,500-word critical reflection. Deadline: 15 January 2027 at 3pm.
Part 260%Knowledge Organisation System and formal description guidelines, with a technical schema and 1,500-word report. Deadline: 12 April 2027 at 3pm.

The official 2026/27 Moodle assessment page publishes Part 1 at 40% and Part 2 at 60%; the numeric rows total 100%.

INST0089 assessment weightsPart 1 occupies forty percent and Part 2 occupies sixty percent of the module assessment.PART 140%PART 260%Published coursework weighting for academic year 2026/27
Other students are asking · INST0089

What other students are asking about INST0089

Where can I find lecture notes or study guides for INST0089 at ucl?
The INST0089 study guide in AskSia Library covers Information Organisation and Description in 6 chapters, with the assessment table, a chapter-by-chapter topic map, key terms and a worked example, free to read on this page.
Is there a final exam in INST0089?
No final exam is listed in the offering this AskSia Library guide is built from; INST0089 is assessed by Part 1 40%, Part 2 60%.
What does INST0089 cover on metadata properties and contexts?
In AskSia Library's INST0089 guide, the Metadata Properties and Contexts chapter explains week 2: property-value statements, domain fields, value rules, machine processing and user action.
What does INST0089 cover on standards and interoperability?
In AskSia Library's INST0089 guide, the Standards and Interoperability chapter explains week 3: structure, content, value and exchange rules, crosswalks and bounded interoperability.
What does INST0089 cover on dublin core record design?
In AskSia Library's INST0089 guide, the Dublin Core Record Design chapter explains week 3: Simple Dublin Core element selection, value control, relationships and record auditing.
Weights, dates and every chapter are set out with their sources further down this page.
Current dates · verify in LMS

Current INST0089 dates

DateItemControl
15 January 2027, 3pmPart 1 deadlineThe component contributes 40% of the module result.
12 April 2027, 3pmPart 2 deadlineThe component contributes 60% of the module result.

The dates and weights come from the captured 2026/27 Moodle assessment page. Confirm exact deadlines and submission settings in the live LMS.

Contents · every chapter, one map

What INST0089 covers

Six connected chapters move from purposeful description through metadata, standards, Dublin Core and XML to the evidence chain required for the module coursework.

01

Description for Identity and Use

Week 1: resource boundaries, identity, content, context, disambiguation, findability and reuse.

Description for Identity and Use begins with the resource rather than the form. A record must make clear what is being described, which level or boundary applies and what another person or system should be able to do.

  • Unit of description and descriptive boundary
  • Identity, content and context
  • Disambiguation and distinctive features
  • Findability through searchable controlled values
  • Reusability through rights, provenance and documentation
  • Audience tasks and sufficient granularity
In the full guide: 3 pages · 2 practice questions · 2 figures
02

Metadata Properties and Contexts

Week 2: property-value statements, domain fields, value rules, machine processing and user action.

Metadata Properties and Contexts treats the property-value statement as the basic unit of structured description. A property supplies meaning, the value supplies content and a rule states how the value is formed.

  • Metadata as structured encoded description
  • Property-value statements and semantics
  • Data dictionaries and value rules
  • Controlled values and free text
  • Domain-specific metadata requirements
  • Machine processing and user action
In the full guide: 3 pages · 2 practice questions · 2 figures
03

Standards and Interoperability

Week 3: structure, content, value and exchange rules, crosswalks and bounded interoperability.

Standards and Interoperability separates the different agreements that allow records to move and remain meaningful. A standard may govern data structure, descriptive content, permitted values or exchange.

  • Structure, content, value and exchange standards
  • Semantic and technical interoperability
  • Crosswalk design and transformation rules
  • Exact, broad and lossy mappings
  • Local extensions and documented loss
  • Versioning, governance and review
In the full guide: 4 pages · 2 practice questions · 2 figures
04

Dublin Core Record Design

Week 3: Simple Dublin Core element selection, value control, relationships and record auditing.

Dublin Core Record Design applies a broad element set without treating it as a checklist.

  • Simple Dublin Core element set
  • Creator and Contributor roles
  • Subject and Description values
  • Type and Format distinctions
  • Identifier, Source and Relation
  • Coverage, Rights and value evidence
In the full guide: 3 pages · 2 practice questions · 2 figures
05

XML Structure and Validation

Week 4: XML trees, elements, attributes, hierarchy, well-formedness and semantic review.

XML Structure and Validation presents XML as a metalanguage for making document and data structure explicit. Elements create named containers and hierarchy, attributes qualify elements and values carry content.

  • XML as extensible markup
  • Root and child element structure
  • Attributes and qualified values
  • Proper nesting and well-formedness
  • Schema rules and validation evidence
  • Semantic and scenario testing
In the full guide: 4 pages · 2 practice questions · 2 figures
06

Encoding Project and Critical Reflection

Assessment 1: one metadata standard, two scenario-led formats, validation evidence and critical evaluation.

Encoding Project and Critical Reflection turns the module concepts into an evidence-driven design project.

  • Resource boundary and complete resource collection
  • Audience tasks and scenario constraints
  • One standard across two formats
  • CSV, XML and JSON trade-offs
  • Validation evidence and documentation
  • Critical evaluation and FAIR improvement
In the full guide: 4 pages · 2 practice questions · 2 figures

They support disambiguation, discovery and reuse when values are accurate, traceable and formed according to clear rules.

The next stage turns description into metadata. Properties give values meaning, while schemas and vocabularies help records become consistent and machine-processable. The module distinguishes the conceptual standard from the format used to package it.

Students examine why domain context changes the fields that matter, how shared standards support exchange and where mappings compress local meaning. Simple Dublin Core provides a compact element set for practising decisions about titles, creators, subjects, dates, types, formats, identifiers, sources, relations, coverage and rights.

XML makes structure explicit through elements, attributes, values and hierarchy.

Technical checks such as well-formedness and schema validation are essential, but they cannot prove that a record describes the right resource or uses a property correctly. Semantic review and scenario testing remain necessary.

This distinction is central to the coursework, which asks students to hold metadata meaning steady while representing one resource collection in different formats for different users.

The assessment has two coursework parts. Part 1 is worth 40% and combines a metadata encoding project with a 1,500-word critical reflection.

Part 2 is worth 60% and asks students to devise and defend a Knowledge Organisation System with formal description guidance, a technical schema and a 1,500-word report. Strong work links every design decision to resource evidence, audience tasks, validation results and an honest account of trade-offs.

Worked example · free

Choose two formats for one metadata model

Q [8 marks]. A community archive needs an internal completeness sheet and a public exchange file for oral-history records. Select formats for both scenarios while keeping the metadata meanings consistent. The marks shown for this archive decision are not a published university allocation.
Assessment evidence chainResource analysis flows through audience, standard, format and validation decisions before reaching evaluation.RESOURCEboundaryAUDIENCEtasksSTANDARDmeaningFORMATpackagingVALIDATEevidenceREFLECTtrade-offsreflection feeds the next design decision
The forward arrows connect each design decision to the next, while the return path shows that evaluation should revise the original resource and audience assumptions.
  • 2Define each interview as the record unit and list audience tasks, relationships, access constraints and value sources.
  • 2Choose one metadata element set and document repeatable subjects, agent roles, identifiers and access values.
  • 2Use CSV for rapid internal scanning and XML for repeated or nested public exchange data, then validate each representation appropriately.
  • 2Evaluate the observed flattening, hierarchy, maintenance and interoperability consequences against the two user scenarios.
The recommendation is conditional: CSV serves the internal review task, while XML preserves the repeated values and typed relationships required for exchange. Both must implement the same documented metadata meanings.
Sia tip — Write the audience task beside each format choice; if the task changes, reconsider the choice instead of defending the file extension.
Glossary

Key terms

Information description
An explicit account of a resource's identity, content and context that enables people or systems to act.
Unit of description
The resource level and boundary that one metadata record describes.
Metadata property
A named characteristic or relationship that gives a recorded value its meaning.
Value rule
A documented instruction governing how values for a property are formed or selected.
Controlled vocabulary
An authorised set of terms used consistently for a defined descriptive purpose.
Metadata standard
A formal agreement about data structure, content, values or exchange for a stated purpose.
Interoperability
The ability of systems or communities to exchange and meaningfully use information for defined tasks.
Crosswalk
A documented mapping between properties or values in two metadata schemes.
Dublin Core
A broad metadata element set used to describe resources across many domains.
XML element
A named XML structure with content or child nodes enclosed by tags.
XML attribute
A named qualifier attached to an XML element as an attribute value.
Well-formedness
Compliance with XML syntax rules such as one root, proper nesting and matched tags.
Schema validation
Testing a document against declared rules for allowed structure, order, repetition and data types.
FAQ

INST0089 FAQ

How difficult is this module?

The captured teaching points to sustained design judgement rather than a published difficulty rating. Students must keep resource boundaries, metadata meanings, audience tasks and technical representations aligned. The first coursework also requires two encodings plus a concise critical report, so a decision log and early validation are more useful than leaving the technical work until the writing stage.

What is the assessment structure?

Part 1 contributes 40% and combines a metadata encoding project with a 1,500-word critical reflection. Part 2 contributes 60% and asks for a Knowledge Organisation System, formal description guidelines, a technical schema and a 1,500-word report. The published deadlines are 15 January 2027 and 12 April 2027, both at 3pm.

What is the difference between a metadata standard and a format?

A metadata standard defines meanings, properties, relationships or value rules. A format such as CSV, XML or JSON packages those meanings in a technical representation. The first coursework asks students to keep one standard stable while comparing two formats, so changing both at once would weaken the evaluation.

How should I choose Dublin Core elements?

Begin with the resource boundary and user task, then select the elements that express the required identity, content, context and relationships. Define value rules for dates, names, subjects, identifiers and rights. Do not fill every optional field automatically or compress repeated values into one ambiguous sentence.

Does XML validation prove that the metadata is correct?

No. Well-formedness and schema validation can confirm syntax and declared structural rules, but they do not prove that a property describes the right resource or carries the right meaning. Add semantic review against the data dictionary and scenario tests that exercise discovery, linking, transformation or reuse.

What makes the critical reflection analytical?

Connect each judgement to a requirement, a design choice, evidence from the files and a consequence for the user. Then acknowledge a limitation and propose a proportionate improvement. Generic claims that one format is powerful or easy remain descriptive until the report shows what was preserved, flattened or made harder in the actual scenario.

How should I plan the first coursework?

Start by analysing the whole selected resource collection, its boundaries, relationships and sensitivities. Design two distinct user scenarios, choose one metadata standard, document fields and value rules, build both encodings and validate them. Write the report from that evidence trail rather than inventing reasons after the files are complete.

Chapter questions

Questions students ask in each INST0089 chapter

Why is a label not enough?
A label usually names a broad class, while a description supplies the identity, content and context needed to distinguish one resource and act on it. Calling something a poster or bottle cannot support reliable recovery, discovery or management until the record adds evidence such as identifiers, dates, relationships, distinctive features and rights. Chapter 01 · Description for Identity and Use
Why is a value meaningless without its property?
The same string can assert different facts. A year might be a creation date, publication date or coverage period, while a name might be a creator, subject or record author. The property and its definition identify the relationship between the value and the resource, allowing users and software to interpret it consistently. Chapter 02 · Metadata Properties and Contexts
Can matching field labels be mapped automatically?
Not safely. Two systems may use the same label for different relationships, such as a rights holder and a physical custodian both called Owner. Compare definitions, record subjects, value rules and examples before declaring equivalence. A label match is evidence to investigate, not proof of semantic identity. Chapter 03 · Standards and Interoperability
Do I need to fill every Dublin Core element?
No. Select elements supported by evidence and required by the user scenario. An optional field filled with a guess or repeated boilerplate reduces quality. Document intentional omissions and blank states, especially where attribution, rights or sensitive information limits what can be asserted or published. Chapter 04 · Dublin Core Record Design
What is the difference between an element and an attribute?
An element can contain text, repeated child elements and richer structure. An attribute adds a concise named qualifier to one element. Projects should choose consistently. Information that needs repetition, nesting or further context usually works better as an element, while a short role or identifier type may fit an attribute. Chapter 05 · XML Structure and Validation
Why must the resource collection be analysed first?
The resource boundary determines which entities, facts and relationships the metadata must represent. If encoding starts before that analysis, fields may mix levels, omit important relations or carry values copied from the wrong source. A clear boundary also makes the later format comparison fair because both representations describe the same thing. Chapter 06 · Encoding Project and Critical Reflection
Study strategy

How to prepare for the assessments

Study the module as one decision chain. First, practise defining a unit of description and separating identity, content and context. Next, turn observations into property-value statements and write short value rules for dates, names, subjects, identifiers and rights. Compare standards by the problems they solve: structure, content, values or exchange.

Build small Dublin Core records from original resources, then audit close element pairs such as Creator and Contributor, Type and Format, and Identifier and Source. For XML, draw the tree before writing tags, validate syntax and structure, and follow with a semantic check. Keep a decision log throughout the coursework with the evidence, audience task, choice, result and limitation for every important field or transformation.

Draft the two scenarios before choosing formats, because a format recommendation is defensible only against a user operation or constraint. Validate early using sample records that include repeated values, missing values and relationships. Write the critical reflection from observed outcomes, not generic format features.

In the final review, trace each claim to a resource fact, task, test or source, then state the practical consequence and the next FAIR improvement.

A+Everything unlocked
Unlocks this Bible + all 32 of your subjects at University College London, plus 1,000+ more Bibles across the AskSia library.
Sia - your INST0089 tutor, unlimited, worked the way the exam marks it
The full 29-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