7AAVIN01 Introduction to Digital Humanities 1
7AAVIN01 Overview
- King's College London
- Semester 1, 2026/27
- Arts and Humanities
- Postgraduate
- 30 credits
- Report and viva
What the module covers
7AAVIN01 Introduction to Digital Humanities 1 is the Semester 1 core module of the MA in Digital Humanities at King's College London, worth 30 credits.
- Assessed by A 2,800-word project report and an individual viva on that report, weighted equally.
- Hardest step Justifying every method choice, because the viva asks why you encoded or described material the way you did.
- How to prepare Choose a project early, use the Week 5 mini-report for feedback and keep research notes for the critical reflection.
What you get in the full 7AAVIN01 Study & Assessment Guide
- 11 chapters, 48 pages — every assessed topic, week by week
- 28 original practice questions, each with a model answer
- 11 worked examples, solved the way 7AAVIN01 marks
- 13 computed figures, redrawn from the course’s own numbers
- Before-you-submit checklist for the 001 Research proposal/report (50%) — 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.
How 7AAVIN01 is assessed
| Component | Weight | Format |
|---|---|---|
| 001 Research proposal/report (2800 words) | 50% | Project report: Option 1 critiques an existing DH project, Option 2 designs one; due 8 December 2026, 14:00 |
| 15-minute viva | 50% | Individual oral discussion of your submitted report with members of the teaching team; no slides |
Both weights come from the module's assessment pattern and the two assignment briefs and total 100%. The submission point currently lists 8 December 2026 at 14:00, while an earlier version of the same page listed 24 November 2026, so confirm the date on KEATS. The module details page names the second component a viva exam based on your report.
Assessment structure
Segment widths reproduce the two published weights, which total 100%.
What other students are asking about 7AAVIN01
- Where can I find lecture notes or study guides for 7AAVIN01 at King's?
- The 7AAVIN01 study guide in AskSia Library covers Introduction to Digital Humanities 1 in 11 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 7AAVIN01?
- No final exam is listed in the offering this AskSia Library guide is built from; 7AAVIN01 is assessed by 001 Research proposal/report (2800 words) 50%, 15-minute viva 50%.
- What does 7AAVIN01 cover on from humanities computing to the big tent?
- In AskSia Library's 7AAVIN01 guide, the From Humanities Computing to the Big Tent chapter explains busa and the punch card operatives, concordances, early societies, SGML and TEI, the web, digitisation and the renaming of the field.
- What does 7AAVIN01 cover on critical and global digital humanities?
- In AskSia Library's 7AAVIN01 guide, the Critical and Global Digital Humanities chapter explains diversity critiques, the English-speaking centre of the field, computational humanities venues and how a search query defines a dataset.
- What does 7AAVIN01 cover on electronic markup, from sgml to tei?
- In AskSia Library's 7AAVIN01 guide, the Electronic Markup, from SGML to TEI chapter explains markup as metainformation, presentational and descriptive markup, generic coding, SGML, XML and the Text Encoding Initiative.
Current 7AAVIN01 dates
| Date | Item | Control |
|---|---|---|
| 15 October 2026 | XML project for feedback | Columbus diary encoding, not formally assessed, due 11:00 PM |
| 20 October 2026 | Extra session on assessment | Online, 11:00 to 12:00 |
| 8 December 2026 | Project report | Due 14:00 at the KEATS submission point |
| 9 December 2026 | Career event | 3pm to 5pm, Waterloo campus |
| 16 and 17 December 2026 | Week 11 seminars | Student presentations in the seminars |
Dates are as published in the Semester 1, 2026/27 KEATS module pages and Week 1 slides. Confirm exact deadlines and submission settings in the live LMS.
What 7AAVIN01 covers
Eleven chapters follow the module from debates about the field through markup and metadata to the report and viva.
What Digital Humanities Is and Does
Competing definitions, Drucker's materials, processing and presentation, Berry's waves and the DH project as a trading zoneWhat Digital Humanities Is and Does starts where the module starts: with disagreement.
- Competing definitions of the field
- Drucker's materials, processing and presentation
- Davidson's Humanities 1.0 and 2.0
- Berry's three waves
- The DH project versus the lone scholar
- Trading zones between disciplines
From Humanities Computing to the Big Tent
Busa and the punch card operatives, concordances, early societies, SGML and TEI, the web, digitisation and the renaming of the fieldFrom Humanities Computing to the Big Tent follows the brief history in the Week 1 lecture.
- Busa and the Index Thomisticus
- The punch card operatives
- Concordances, corpora and authorship
- Journals, societies and the Oxford Text Archive
- SGML, TEI and hypertext
- The web, digitisation and the semantic web
Critical and Global Digital Humanities
Diversity critiques, the English-speaking centre of the field, computational humanities venues and how a search query defines a datasetCritical and Global Digital Humanities covers the part of the Week 1 lecture that turns the field's questions on itself.
- Diversity as an internal critique
- Geographic and linguistic imbalance
- GO::DH and Around DH in 80 Days
- Computational humanities venues
- AI in humanities research
- How a search query defines a dataset
Electronic Markup, from SGML to TEI
Markup as metainformation, presentational and descriptive markup, generic coding, SGML, XML and the Text Encoding InitiativeElectronic Markup, from SGML to TEI explains what markup is and where it came from. It starts with the dictionary senses of markup and the idea of metainformation, with four conditions a markup system must meet.
- Dictionary senses of markup
- Metainformation and its conditions
- Presentational, procedural and descriptive markup
- Generic coding and GenCode
- SGML as a metalanguage
- HTML, XML and XHTML
Writing Well-Formed XML in Oxygen
Root elements, nesting, naming rules and attributes, the recipe exercise, reading Oxygen's error indicators and validationWriting Well-Formed XML in Oxygen turns the Week 2 practical into a method.
- Elements, start tags and end tags
- One root element
- Nesting without overlap
- Naming rules and case
- Attributes in the start tag
- The recipe exercise in Oxygen
Encoding a Humanities Text: Columbus's Diary
Document analysis, hierarchical and in-line markup, names and persons, container elements, footnotes and automationEncoding a Humanities Text: Columbus's Diary works through the main Week 2 workshop, in which groups mark up an English translation of Columbus's journal in stages.
- Document analysis before tagging
- Metadata and high-level structure
- Templates built in logical order
- In-line markup of places and people
- Name or person
- Containers for repeating entries
Evaluating Markup Projects
Questions for any digital edition, what an encoding enables, documentation, case studies and writing a specific critiqueEvaluating Markup Projects prepares you for the critique option of the report.
- The four allocated projects
- Preparation questions for any project
- What the XML enables
- Documentation and encoding guidelines
- Further case studies
- From seminar notes to a critique
Metadata Types, Audiences and Purposes
Which object a record describes, descriptive to structural metadata, audiences, personas and the four user tasksMetadata Types, Audiences and Purposes covers the first half of Week 3. It begins with the question of which object a record describes, defines metadata as data that describes other data, and shows how much it reveals, from phone records to the location data in a photograph.
- Which object does the record describe
- Metadata as data about data
- Metadata already in your files
- Five types of metadata
- Audience and purpose
- The persona activity
Metadata Standards, Vocabularies and MODS
Technical, structure, value and content standards, Dublin Core, controlled vocabularies and the upgrade to MODSMetadata Standards, Vocabularies and MODS covers the second half of the Week 3 lecture and its seminar.
- Why invented tags cannot combine
- Technical, structure, value and content standards
- The fifteen Dublin Core elements
- DCMI Terms for precise dates
- Choosing a structure standard
- Controlled vocabularies and identifiers
Metadata Quality, Ethics and Linked Data
Accuracy, completeness, provenance, timeliness and accessibility, the ethics of description and the move to linked dataMetadata Quality, Ethics and Linked Data closes the metadata block and opens Week 4. It sets out five quality criteria, accuracy, completeness, provenance, timeliness and accessibility, and applies them to a record.
- Accuracy and completeness
- Provenance of values
- Timeliness and accessibility
- Ethics of description cases
- Rewrite, annotate or keep
- Metadata beyond the academy
The Project Report and the Viva
Report options and sections, marking criteria, AI and referencing rules, formative steps and the individual vivaThe Project Report and the Viva brings the module's methods to its two assessment components.
- Option 1 and Option 2
- Required sections and word caps
- Marking criteria
- Referencing and AI deductions
- Formative mini-report
- Viva practice and presentations
It introduces the digital humanities both as a discipline and as a loose family of ways of making knowledge, and asks what digital and computational methods can do for the study of culture, in fields as different as linguistics, history, music and heritage.
The tools it uses require no prior technical knowledge.
How the teaching unfolds
The opening week surveys definitions, histories and critiques of the field: Busa's corpus and the women who entered its data, the move from humanities computing to digital humanities, questions of diversity and language, and the rise of computational humanities. Week 2 is practical.
You learn electronic markup, from generic coding and SGML to XML and the Text Encoding Initiative, edit XML in the Oxygen editor, encode an English translation of Columbus's diary in groups and evaluate an existing markup project. Week 3 turns to metadata: its types and audiences, Dublin Core and MODS records, controlled vocabularies such as the Getty AAT, quality criteria and the ethics of description.
Week 4 asks how linked data connects collections, and later weeks connect with the Python skills taught in Coding and the Humanities.
How it is assessed
Two components carry equal weight. A 2,800-word report, worth 50%, either critiques an existing digital humanities project with proposals for improvement or designs a project that answers a humanities research question with methods from the module.
An individual 15-minute viva, worth the other 50%, follows submission and examines your understanding of the report and your reasons for every choice in it. Formative steps along the way are a Week 5 mini-report, viva practice in pairs and a short presentation with slides.
How to use this guide
Work through the method chapters with a project in mind.
Every chapter ends with practice that includes viva-style questions, and the final chapter turns the brief's sections, criteria and deductions into a plan you can check before you submit.
Worked example · free
Structure a diary for XML
- 1Start from one root element, journal, that contains a header and a body.
- 1Put the title and editor in the header, since they describe the document rather than form its text.
- 1Inside the body, order the introduction, the entries and the notes as the document presents them.
- 1Repeat one entry element for every day instead of numbering names such as entry1 and entry2.
- 1Place each date in a date element inside its entry, or in an attribute, so entries can be sorted.
Key terms
- Digital humanities
- A field that uses digital and computational methods to study culture and examines those methods critically.
- Descriptive markup
- Markup that names what each part of a text is and leaves its appearance to a separate process.
- XML
- A simplified form of SGML, released in 1998, used to write structured, machine-readable documents.
- Text Encoding Initiative
- A consortium and its XML guidelines for encoding texts, with about 500 elements.
- Well-formed document
- An XML file that follows the basic syntax rules: one root, closed elements and no overlap.
- Attribute
- A name and quoted value in an element's start tag that adds information about the element.
- Metadata
- Data that exists to describe other data and to tell you about it.
- Dublin Core
- A deliberately limited standard of fifteen general elements for describing resources.
- MODS
- A library metadata standard that adds roles, subject authorities, places and kinds of date.
- Controlled vocabulary
- A list giving one preferred term and identifier for each concept, such as the Getty AAT.
- Provenance
- The record of where a value in a record came from: a crowd, an expert or a machine.
- Linked data
- An approach that joins records across collections through shared web identifiers.
- Viva
- An oral examination in which you discuss and justify your submitted report.
7AAVIN01 FAQ
How is Introduction to Digital Humanities 1 assessed?
Two components count equally. A 2,800-word project report is worth 50%, and an individual 15-minute viva on that report is worth the other 50%. Formative tasks, including a Week 5 mini-report, viva practice in pairs and a short presentation, give feedback without counting towards the mark.
What are the two options for the project report?
Option 1 critiques an existing digital humanities project, especially by proposing improvements to its markup, digitisation, metadata or data robustness. Option 2 designs a project to answer a research question in a humanities discipline, using methods the module teaches. Each option has its own required sections, and the title must state your sector or discipline.
What happens in the viva?
After you submit, you meet members of the teaching team for an individual 15-minute academic discussion of your report. It is not a presentation and needs no slides. Expect questions on your aims, methods and their limitations, your sources, results, ethical or technical challenges, alternatives and future development, and any AI use you declared.
Can I use generative AI for the report?
The brief permits AI use at the minimal level only, and you must include an AI declaration of up to 200 words describing any use. Hallucinated facts or references each cost at least 5%, a missing declaration costs 5%, and suspected undeclared use leads to an Academic Integrity Meeting, so verify everything you submit.
What referencing rules does the report have?
You must engage with at least two quotations from the module reading list, with page numbers where applicable, or lose 5%. Roughly half of your references should carry page numbers, bibliography entries need working links when the source is online, and the bibliography and appendix are not counted in the 2,800 words.
When is the project report due?
The KEATS submission point lists 8 December 2026 at 14:00. An earlier version of the same page showed 24 November 2026, so check the live page before planning. The programme induction explains that work up to 24 hours late loses 10 raw marks and later work fails the module.
Do I need programming or technical experience?
No prior technical knowledge is required for the tools the module uses, such as the Oxygen XML editor. Python is taught in the linked module Coding and the Humanities, and if your report uses code, the brief asks you to include it in an appendix and explain how it supports your research aims.
Questions students ask in each 7AAVIN01 chapter
- Is there one accepted definition of digital humanities?
- No single definition settles the debate. The lecture sets enthusiastic, sceptical and political verdicts side by side, and Kirschenbaum's phrase about a free-floating signifier captures why. A report should state a working definition and show how it shapes the analysis. Chapter 01 · What Digital Humanities Is and Does
- Why are Busa's punch card operatives important?
- They carried out the data entry for the Index Thomisticus but were left out of official documentation and later histories. Terras and Nyhan recovered their labour, which raises the question of who receives credit in digital projects. Chapter 02 · From Humanities Computing to the Big Tent
- How diverse is the digital humanities community?
- Galina Russell found it is drawn mainly from a few English-speaking countries, as academia is generally. The lecture also asks about race, class, gender, sexuality, disability and alternative histories beyond the Anglophone world. Chapter 03 · Critical and Global Digital Humanities
- What is the difference between presentational and descriptive markup?
- Presentational markup controls how text looks, as a WYSIWYG editor does. Descriptive markup records what each part of a text is, such as a title or a foreign phrase, and lets a separate process decide its appearance. Chapter 04 · Electronic Markup, from SGML to TEI
- What does well-formed mean in XML?
- A well-formed file follows the basic syntax: one root element, every element closed, no overlapping elements and legal names. Oxygen shows a green box when this holds and a red one when it does not. Chapter 05 · Writing Well-Formed XML in Oxygen
- Why should I not number element names in XML?
- Names such as entry1 and entry2 are neither helpful nor sustainable, because software cannot treat them as one kind of thing. Use one element name and, if the original numbering matters, record it in an attribute. Chapter 06 · Encoding a Humanities Text: Columbus's Diary
- Which projects are assessed in the Week 2 preparation?
- Students are allocated by surname to an edition of the Wilde manuscript of Dorian Gray, the guidelines for Edvard Munch's writings, a TAPAS drama sample or the Mark Twain project, and assess its use of XML. Chapter 07 · Evaluating Markup Projects
- What are the five types of metadata?
- Descriptive metadata says what an item is and is about; administrative covers management and rights; technical records how the file was made; preservation records how it is kept usable; structural records how its parts fit together. Chapter 08 · Metadata Types, Audiences and Purposes
- What are the four kinds of metadata standard?
- Technical standards fix the syntax, such as XML or JSON. Structure standards fix the fields, such as Dublin Core or MODS. Value standards fix the words, such as the Getty AAT, and content standards fix how values are written, such as CCO. Chapter 09 · Metadata Standards, Vocabularies and MODS
- What are the five criteria for metadata quality?
- Accuracy asks whether values are correct and well sourced, completeness whether the essentials are described for the audience, provenance where values came from, timeliness whether terms are current, and accessibility whether people can understand the record. Chapter 10 · Metadata Quality, Ethics and Linked Data
- What are the two options for the report?
- Option 1 is a critique of an existing DH project, especially suggesting improvements to its markup, digitisation, metadata or data robustness. Option 2 designs a project around a research question in a humanities discipline, using module methods. Chapter 11 · The Project Report and the Viva
How to prepare for the assessments
Treat the module as preparation for one project you will have to defend twice, once in writing and once in conversation. Choose a candidate project in the first weeks and test each method against it as you learn it: what would markup add, which metadata standard would fit, which quality criteria would it fail.
Keep research notes from the start, recording decisions, problems and what you learned, because the critical reflection and the viva both draw on them. Use the Week 5 mini-report to check feasibility and the link to module methods, then rehearse viva questions in pairs using that feedback.
Before submission, check your plan against the brief's numbers: the 2,800-word total, the Option 2 section caps, two reading-list quotations with page numbers and the AI declaration. In the days before the viva, reread your report section by section and prepare a reason, a limitation and a next step for each one.