Skip to content
julsraemyPublic

About

PhD Website - Linked Open Usable Data for Cultural Heritage

Topics

Resources

Stars

0 stars

Watchers

1 watching

Forks

Repository files navigation

Linked Open Usable Data for Cultural Heritage

DOI

A website about my PhD thesis on Linked Open Usable Data (LOUD), with an HTML version of the thesis: https://phd.julsraemy.ch

Title: Linked Open Usable Data for Cultural Heritage: Perspectives on Community Practices and Semantic Interoperability

Cite as

Raemy, J. A. (2026). Linked Open Usable Data for Cultural Heritage: Website and HTML Version of the PhD Thesis (Version 1.0) [Computer software]. Zenodo. https://doi.org/10.5281/zenodo.24304125

To cite the thesis itself: Raemy, J. A. (2024). Linked Open Usable Data for Cultural Heritage: Perspectives on Community Practices and Semantic Interoperability [PhD thesis, University of Basel]. https://hdl.handle.net/20.500.14716/148352

Running the site

The site is built with 11ty and searched with Pagefind.

npm install        # once
npm run build      # build the site into _site/ and create the search index
npm start          # serve on http://localhost:8080/ and rebuild on changes

Run npm run build at least once before npm start, so that the search index exists (npm run search-index refreshes it). After editing .eleventy.js itself, restart npm start: the dev server can otherwise keep serving pages built with the old configuration. Pushing to main builds and deploys the site to GitHub Pages (.github/workflows/deploy.yml); _site/ is not committed.

Where things are

What Where
Thesis landing page (title, abstract, table of contents) src/thesis.md → /thesis.html
Chapters, front and back matter src/thesis/*.md → /thesis/*.html
Bibliography data (CSL-JSON, exported from Zotero) src/utils/bib-data.json
Acronyms src/data/acronyms.json
Research outputs (CSL-JSON, also served at /data/research.json) src/data/research.json
Layouts and sidebar src/_includes/
Build logic (citations, acronyms, ToC, viewers…) .eleventy.js, src/utils/, src/_data/thesisToc.js
Styles and scripts assets/stylesheets/style.css, src/js/
Linked Art records (see below) src/linked-art.11ty.js, src/utils/linked-art-content.js

Linked Art

The thesis and its chapters are also published as Linked Art JSON-LD, following the Linked Art API 1.0:

  • /linked-art/text/thesis.json: the thesis (LinguisticObject, classified as Thesis), with its abstract, DOI, Handle and publication;
  • /linked-art/text/thesis/<chapter>.json: each chapter (part_of the thesis), with its full text as HTML in content;
  • /linked-art/person/julsraemy.json: the author.

The records are generated at build time from the same sources as the HTML pages: their structure is defined in src/linked-art.11ty.js (add properties or AAT terms there), and the chapter text is copied from the built pages by src/utils/linked-art-content.js. Each thesis page links to its record (“Linked Art (JSON-LD)” in the sidebar and a <link rel="alternate"> in its head).

Writing conventions

  • Chapters: each file in src/thesis/ has front matter with title and chapter (number); front and back matter pages use part: "front" or "back" and order. The sidebar, the table of contents, the prev/next links and the lists of figures, tables and code snippets are generated from the files.
  • Headings carry their number and an id, e.g. ## 3.1 What Makes Cultural Heritage Data Stand Out? {id="sec:standout"}. Links such as [Section 3.1](#sec:standout) work across chapters: they are rewritten to the right page at build time.
  • Citations use Pandoc syntax with keys from bib-data.json: [@key], [@key p. 4], [@a; @b], [-@key], and narrative @key or @key [p. 4]. Each citation links to its entry in the chapter's references and in the full bibliography.
  • Acronyms are written as plain text (IIIF, APIs); every occurrence listed in acronyms.json is marked up and linked to the Acronyms page automatically.
  • Footnotes use [^n] and keep their number on the page.
  • Figures, tables and code snippets are <figure id="fig:…">, "tab:…" or "lst:…" with a caption starting with <strong>Figure 3.1</strong>:; code goes in fenced code blocks inside the figure.
  • IIIF viewers (pages with viewers: true in their front matter): {% mirador "manifest-url", "caption" %} and {% iiifImage "info.json-url", "caption", "description" %}.
  • Research outputs: add a CSL-JSON item to src/data/research.json and place it on src/research.md with {% researchItem "id" %}; the APA reference, COinS and JSON-LD are generated.

About

PhD Website - Linked Open Usable Data for Cultural Heritage

Topics

Resources

Stars

0 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages